On 9/9/16 11:47 PM, Zorro Lang wrote: > The man 8 xfs_repair said "xfs_repair run without the -n option will > always return a status code of 0". That's not correct. > > xfs_repair will return 2 if it find valuable metadata changes in log > which needs to be replayed, 1 if it can't fix the corruption or some > other errors happened and 0 if nothing wrong or all the corruptions > were fixed. > > Generally xfs_repair -L will always return 0, except it can't clear > the log. And I think that's an operational type error, not the result of a filesystem problem; more like an IO error, or a code bug, I *think* ... more below. > Signed-off-by: Zorro Lang <zlang@xxxxxxxxxx> > --- > > Hi, > > I trusted the xfs_repair manpage, and thought xfs_repair will always return 0. > But recently I found it lies when I tried to review someone xfstests case. > > A correct manpage will help more people to write right cases, so I try to modify > the manpage, by search all exit/do_error in xfsprogs/repair. I'm not the best > one who learn about xfs_repair, so I just hope I did the right thing:-P Please > feel free to correct me. > > Thanks, > Zorro > > man/man8/xfs_repair.8 | 13 ++++++++++++- > 1 file changed, 12 insertions(+), 1 deletion(-) > > diff --git a/man/man8/xfs_repair.8 b/man/man8/xfs_repair.8 > index 1b4d9e3..1f8f13b 100644 > --- a/man/man8/xfs_repair.8 > +++ b/man/man8/xfs_repair.8 > @@ -504,12 +504,23 @@ that is known to be free. The entry is therefore invalid and is deleted. > This message refers to a large directory. > If the directory were small, the message would read "junking entry ...". > .SH EXIT STATUS > +.TP > .B xfs_repair \-n > (no modify node) > will return a status of 1 if filesystem corruption was detected and > 0 if no filesystem corruption was detected. > +.TP > .B xfs_repair > -run without the \-n option will always return a status code of 0. > +run without the \-n option will return a status code of 2 if it find the > +filesystem has valuable metadata changes in log which needs to be > +replayed, 1 if there's corruption left to be fixed I'm not sure that's the best description; from a quick look, I think those exit values of 1 result from do_error(), and in repair that's (usually?) due to something like a memory allocation failure, or an inconsistent state in the tool; more like hitting an ASSERT. That might leave corruption, but only as a follow-on effect. > + or can't find log head > +and tail or some other errors happened, Which is the same as above, I think - an internal error. > and 0 if nothing wrong or all the > +corruptions were fixed. > +.TP > +.B xfs_repair \-L > +(Force Log Zeroing) > +will return a status code of 1 if it can't clear the log, or will always > +return 0. How about something like this: .B xfs_repair \-n (no modify node) will return a status of 1 if filesystem corruption was detected and 0 if no filesystem corruption was detected. .TP .B xfs_repair run without the \-n option will return a status code of 2 if it finds a filesystem log which needs to be replayed (by a mount/umount cycle), 1 if a runtime error is encountered, and 0 in all other cases, whether or not filesystem corruption was detected. and I'd leave out the bit about xfs_repair -L; really that's just a runtime error - if we clear the log and then can't find the head/tail, something strange has gone wrong. Thanks, -Eric > .SH BUGS > The filesystem to be checked and repaired must have been > unmounted cleanly using normal system administration procedures > _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
