| To: | Marco Berizzi <pupilla@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS: 2.6.26-rc6 link count mismatch for inode |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Thu, 19 Jun 2008 02:12:52 +1000 |
| Cc: | linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx |
| In-reply-to: | <BAY103-DAV69C0718B7EDB534D9337FB2A90@phx.gbl> |
| Mail-followup-to: | Marco Berizzi <pupilla@xxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx |
| References: | <BAY103-DAV69C0718B7EDB534D9337FB2A90@phx.gbl> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.17+20080114 (2008-01-14) |
On Mon, Jun 16, 2008 at 11:11:31AM +0200, Marco Berizzi wrote: > Hi Folk, > > I was tring to compile firefox 3.0rc3 > and while I was erasing a previous > /tmp/mozilla tree, I started a new > tar xjf mozilla-blabla. > After a while linux 2.6.26-rc6 was > unresponsive: I have unplugged the > power cable. No problem at startup, > but: What are your mount options? Are you using barriers (what does XFS output in dmesg when mounting the filesystem)? I ask because I've seen this sort of directory corruption before when using volatile write caches and yanking the power.... i.e. the corruption could have been caused by the way you reset the system, not because of the hang. Do you have any information on what caused the hang? Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Directory mtime update issue (kernel 2.6.25), Michael-John Turner |
|---|---|
| Next by Date: | Re: Directory mtime update issue (kernel 2.6.25), Christoph Hellwig |
| Previous by Thread: | XFS: 2.6.26-rc6 link count mismatch for inode, Marco Berizzi |
| Next by Thread: | Re: XFS: 2.6.26-rc6 link count mismatch for inode, Marco Berizzi |
| Indexes: | [Date] [Thread] [Top] [All Lists] |