On Tue, Feb 04, 2014 at 10:23:10PM +0600, Roman Mamedov wrote: > Hello, > > My server had a period of instability (PSU-related issues), some lockups, > some strange crashes, and some files became corrupted, and perhaps parts of > a filesystem too. One BTRFS partition now fails with the following errors. > > On an attempt to make a snapshot: > > [ 48.035664] btrfs: corrupt leaf, bad key order: block=193529446400,root=1, > slot=9 [snip]
Bad key order is pretty much always down to hardware corrupting data at some point -- which would go well with your list of hardware problems above. > Currently I have it mounted read-only, and all data seems to be accessible. > Short of copying everything away and recreating the FS, how can I bring it to > a working order. Is btrfsck a good option here? The first investigation to do would be to look at the block in question and see if it's got an obvious problem with it. If you post the output of "btrfs-debug-tree -b 193529446400 /dev/whatever", we can take a look at the indexing. Hugo. -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- You're never alone with a rubber duck... ---
signature.asc
Description: Digital signature
