2017-06-07 11:48 GMT+03:00 Stefan G. Weichinger <[email protected]>: > > greets > > I have a customer server that was set up with a hardware raid and on top > of that /dev/sda exists a btrfs filesystem. > > Yes, I know, that is stupid (can't change that easily). > > In dmesg I get flooding: > > [2329426.792480] BTRFS warning (device sda): csum failed ino 7454384 off > 81708052480 csum 3746940842 expected csum 3305376500 > [2329427.844757] BTRFS warning (device sda): csum failed ino 7454384 off > 81708052480 csum 3746940842 expected csum 3305376500 > [2329428.929354] BTRFS warning (device sda): csum failed ino 7454384 off > 81708052480 csum 3746940842 expected csum 3305376500 > > ... > > I googled how to spot the file containing that problematic block(?): > > find / -type f -exec cp {} /dev/null \; > > I have that running within tmux now, are there any other ways to find > that file and somehow fix it? > > That btrfs contains the root-fs of the server ... so I would maybe have > to driver there, boot from stick or so and btrfsck the unmounted fs? > > thanks, Stefan
btrfs scrub start /mnt_path do this trick After, you can find info with paths in dmesg -- Have a nice day, Timofey. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
