| To: | Steve Lord <lord@xxxxxxx> |
|---|---|
| Subject: | [xfs-masters] Re: potential xfs_repair bug |
| From: | Junfeng Yang <yjf@xxxxxxxxxxxx> |
| Date: | Thu, 2 Sep 2004 13:47:49 -0700 (PDT) |
| Cc: | xfs-masters@xxxxxxxxxxx, Eric Sandeen <sandeen@xxxxxxx> |
| In-reply-to: | <41377B4F.9040809@xxxxxxx> |
| Reply-to: | xfs-masters@xxxxxxxxxxx |
| Sender: | xfs-masters-bounce@xxxxxxxxxxx |
> > > > I suspect what you are doing with this change is making repair fail > > in the middle of creating the lost+found dir, repair always does that. > > Hi Steve, you mean xfs_repair creates lost+found everytime it runs? I'm not sure if the crash happens in the middling of creating lost+found, as our checker only sees block writes with little file system knowledge. We caught this warning automatically (w/o chaing the xfs_repair code). so is it true that in the rare case that xfs_repair fails in the middle of creating lost+found, '/.' can be wiped off? do you guys consider this as a bug? thanks, -Junfeng |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [xfs-masters] Re: potential xfs_repair bug, Steve Lord |
|---|---|
| Next by Date: | [xfs-masters] Make $314, f_duffytm |
| Previous by Thread: | [xfs-masters] Re: potential xfs_repair bug, Steve Lord |
| Next by Thread: | [xfs-masters] Re: potential xfs_repair bug, Steve Lord |
| Indexes: | [Date] [Thread] [Top] [All Lists] |