| To: | xfs-masters@xxxxxxxxxxx, yjf@xxxxxxxxxxxxx |
|---|---|
| Subject: | [xfs-masters] Re: potential xfs_repair bug |
| From: | Steve Lord <lord@xxxxxxx> |
| Date: | Thu, 02 Sep 2004 14:40:24 -0500 |
| Cc: | Eric Sandeen <sandeen@xxxxxxx> |
| In-reply-to: | <Pine.GSO.4.44.0409021221290.13610-100000@xxxxxxxxxxxxxxxxxxxxx> |
| References: | <Pine.GSO.4.44.0409021221290.13610-100000@xxxxxxxxxxxxxxxxxxxxx> |
| Reply-to: | xfs-masters@xxxxxxxxxxx |
| Sender: | xfs-masters-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla Thunderbird 0.7.1 (X11/20040626) |
Junfeng Yang wrote: > the image was created by > 1. mkfs.xfs -q -d agcount=2 > 2. create one file with a 255-char long name in dir '/' > 3. umount to sync the modifiction > > in other words, this image is a prefectly valid one. presumably, > xfs_repair shouldn't repair anything at all. > > 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. Steve |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [xfs-masters] Re: potential xfs_repair bug, Junfeng Yang |
|---|---|
| Next by Date: | [xfs-masters] Re: potential xfs_repair bug, Steve Lord |
| Previous by Thread: | [xfs-masters] Re: potential xfs_repair bug, Junfeng Yang |
| Next by Thread: | [xfs-masters] Re: potential xfs_repair bug, Steve Lord |
| Indexes: | [Date] [Thread] [Top] [All Lists] |