| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: cache_purge: shake on cache 0x5880a0 left 8 nodes!? |
| From: | Paul Slootman <paul@xxxxxxxxxx> |
| Date: | Sat, 12 Aug 2006 11:14:51 +0200 |
| In-reply-to: | <20060811090218.GB22934@xxxxxxxxxx> |
| References: | <20060810164222.GA16332@xxxxxxxxxx> <200608110125.LAA18091@xxxxxxxxxxxxxxxxxxxxxxx> <20060811090218.GB22934@xxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.12-2006-07-14 |
On Fri 11 Aug 2006, Paul Slootman wrote: > > Unfortunately, the filesystem panicked again last night. > This was after the double repair, and rebooting into 2.6.17.7, which > shouldn't have the bug, right? > I'll run another repair now :-( And again. Curious fact appeared: the lost+found directory from the first time (which I had moved to lost+found.x) could not be removed "Directory not empty". This would indicate that the CVS repair version (of 2 days ago) does not properly build the lost+found directory. I've now zapped that directory with xfs_db, and am running the (daily?!) xfs_repair at this moment. As the filesystem is 1.1TB, it takes a couple of hours :( Paul Slootman |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Negligible improvement when using su/sw for hardware RAID5, expected?, Brian Davis |
|---|---|
| Next by Date: | Bug in xfsrestore or NFS+XFS Filesystem on NFS Server ? Can anyone confirm ?, Juergen Sauer |
| Previous by Thread: | Re: cache_purge: shake on cache 0x5880a0 left 8 nodes!?, Paul Slootman |
| Next by Thread: | XFS internal error XFS_WANT_CORRUPTED_GOTO, Paul Slootman |
| Indexes: | [Date] [Thread] [Top] [All Lists] |