On Mon, Feb 01, 2016 at 03:37:39PM -0500, Austin S. Hemmelgarn wrote: > On 2016-02-01 15:21, Hugo Mills wrote: > >On Mon, Feb 01, 2016 at 02:44:24PM -0500, Austin S. Hemmelgarn wrote: > >>In the process of trying to debug issues I'm having on one of my > >>systems with a new kernel version, I decided to do a dry run check on > >>the root filesystem. 'btrfs check' returned a bunch of lines like: > >> > >>root 257 inode XXXXXX errors 2000, link count wrong > >> unresolved ref dir YYYYY index 53 namelen 3 name LOG filetype 0 > >> errors 3, no dir item, no dir index > >> > >>I got about 20 messages like this with varying values for everything > >>except the filetype and error counts. Based on what I can tell, these > >>look like orphaned inodex, but I'm not certain. > >>Is it safe to tell BTRFS to try and fix these errors? > > > > Yes, those are errors I'd expect btrfs check --repair to handle > >properly. > > > Out of curiosity, do you happen to know if this is how btrfs check > reports orphaned inodes, or is this something else entirely?
I don't know, sorry. Hugo. -- Hugo Mills | We teach people management skills by examining hugo@... carfax.org.uk | characters in Shakespeare. You could look at http://carfax.org.uk/ | Claudius's crisis management techniques, for PGP: E2AB1DE4 | example. Richard Smith-Jones, Slings and Arrows
signature.asc
Description: Digital signature
