Btrfs reports the inode numbers of files with failed checksums. Use `find` to lookup the file names of those inodes. The files may need to be deleted and replaced with backups.
Find which directory in one filesystem that contains most inodes or files. Show Sample Output
XX is your device partition number like /dev/sdc1 .
to see how many inodes your partition have type:
df --inodes (or df -i)
Default formatting with ext4 would create small inode count for the new partition
if you need big count of inodes is the fstype news the correct one.
in debian you can see which fstype exists as template in:
vim /etc/mke2fs.conf
if you format default ext for a partition size with 1TB you would get 1 Million inodes (not enough for backupStorages)
but if you format with fstype news you would get hunderd of millions of inodes for the partition.
you have tune
/etc/sysctl.conf
also with following sysconfig parameters
fs.file-max = XXX
fs.nr_open = XXX
where XXX is the count of max inodes for whole system
Executing pfiles will return a list of all descriptors utilized by the process We are interested in the S_IFREG entries since they are pointing usually to files In the line, there is the inode number of the file which we use in order to find the filename. The only bad thing is that in order not to search from / you have to suspect where could possibly be the file. Improvements more than welcome. lsof was not available in my case Show Sample Output
Filter entries in OpenSuse /var/log/messages like: timestamp servername kernel: [83242.108090] btrfs: checksum error at logical 1592344576 on dev /dev/sda5, sector 5223584, root 5, inode 2652, offset 282624, length 4096, links 1 (path: log/warn) Show Sample Output
btrfs checksum errors console report. Show Sample Output
debian kernel 4.4.6 Show Sample Output
Btrfs reports the inode numbers of files with failed checksums. Use `find` to lookup the file names of those inodes.
commandlinefu.com is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.
Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.
» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10
Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):
Subscribe to the feed for: