On Wed, Apr 12, 2017 at 08:34:05AM +1000, Dave Chinner wrote: > On Tue, Apr 11, 2017 at 04:12:37PM +0200, Jan Tulak wrote: > > A dirty log in an obfuscated dump means that a corruption can happen > > when replaying the log (which contains unobfuscated data). Warn the user > > about this possibility. > > > > The xlog workaround is copy&paste solution from repair/phase2.c and > > other tools, because the function is not implemented in libxlog. > > > > Signed-off-by: Jan Tulak <jtulak@xxxxxxxxxx> > > I think this is overkill. mdrestore is not the place > to be interpreting the state of the dumped image - it is a basic > "restore the image" program, not a "check the validity of the image" > program. > I think that's a reasonable argument for the mdrestore side. I'm less interested in seeing a warning on the restore side in general, personally. I was initially thinking it would have required less code and the whole obfuscation detection thing is getting into hackish territory, to be fair. > Secondly, if people are having problems with running log recovery on > a restored obfuscated image and getting corruption and not knowing > why or what to do, then that is a /documentation and training/ > problem, not a code problem. > > i.e. the problem is that people who aren't developers are trying to > use tools that were written for developers to do forensic analysis > of failures. Don't dumb down the tool for clueless users - point the > users at the documentation that the tool requires to use correctly... > Put me in the clueless users bucket, then. This started with a customer with a corrupted filesystem that provided a metadump that exhibited filesystem corruption. A support person began the process of diagnosing the problem and it eventually got to me, who had to spend a nontrivial amount of time trying to identify what the problem was, see if I could reproduce it on my own to verify it was actually specific to the metadump, etc. This is not an obvious "your metadump is broken" log recovery failure. It's a latent directory corruption that doesn't obviously have anything to do with log recovery in the first place. I'm sure I'll be able to spot it going forward for some time while it's fresh in my mind, but I expect to lose track of that eventually given the rarity (of debugging log recovery issues). It's not reasonable at all to expect regular users or support people to understand this enough to filter out bad images or know when to use or not use a certain combination of metadump options, because it otherwise requires a detailed understanding of XFS logging and directory internals. Brian > Cheers, > > Dave. > -- > Dave Chinner > david@xxxxxxxxxxxxx > -- > To unsubscribe from this list: send the line "unsubscribe linux-xfs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
