On Mon, Jul 01, 2013 at 11:56:30PM +0100, Peter Chant wrote: > Sirs, > > my recently slowing file system is now going read only after trying > a defrag or other operation. I'm wondering whether this is the > result of a hardware failure or a btrfs or some other issue. Output > of dmesg: [snip] > [ 127.862825] btrfs: corrupt leaf, bad key order: > block=2837196627968,root=1, slot=121 [snip] This is usually an indication that you have bad hardware -- I'd suggest testing RAM, PSU, CPU in that order. I'm not sure what, if anything, can be done to fix the error on the disk right now. > Not that I've done anything other than a cursory check but it looks > like the read only data is fine. Might be a good idea to use that to refresh your backups, just in case my prediction about the fixability is correct. 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 --- "How deep will this sub go?" "Oh, she'll go all the way to --- the bottom if we don't stop her."
Attachment:
signature.asc
Description: Digital signature
