Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*XFS\:\s+2\.6\.26\-rc6\s+link\s+count\s+mismatch\s+for\s+inode\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*XFS\:\s+2\.6\.26\-rc6\s+link\s+count\s+mismatch\s+for\s+inode\s*$/: 15 ]

Total 15 documents matching your query.

1. XFS: 2.6.26-rc6 link count mismatch for inode (score: 1): Author: "Marco Berizzi" <pupilla@xxxxxxxxxxx>; Date: Mon, 16 Jun 2008 11:11:31 +0200; 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 un; /archives/xfs/2008-06/msg00163.html (48,848 bytes)
2. Re: XFS: 2.6.26-rc6 link count mismatch for inode (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Thu, 19 Jun 2008 02:12:52 +1000; 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; /archives/xfs/2008-06/msg00199.html (8,972 bytes)
3. Re: XFS: 2.6.26-rc6 link count mismatch for inode (score: 1): Author: "Marco Berizzi" <pupilla@xxxxxxxxxxx>; Date: Wed, 18 Jun 2008 18:39:59 +0200; root@Venus:/etc# cat mtab /dev/sda2 / xfs rw 0 0 root@Venus:/etc# cat fstab /dev/sda2 / xfs defaults 1 1 scsi0 : ahci scsi1 : ahci scsi2 : ahci ata1: SATA max UDMA/133 abar m2048@0xe4809000 port 0xe4; /archives/xfs/2008-06/msg00201.html (11,732 bytes)
4. Re: XFS: 2.6.26-rc6 link count mismatch for inode (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Thu, 19 Jun 2008 14:14:41 +1000; [...] Yeah, it sounds like the I/O subsystem hung somewhere. Without details I can't say what went wrong. If it happens again doing this: To get a dump of all the blocked processes on the console. Th; /archives/xfs/2008-06/msg00207.html (10,653 bytes)
5. Re: XFS: 2.6.26-rc6 link count mismatch for inode (score: 1): Author: "Marco Berizzi" <pupilla@xxxxxxxxxxx>; Date: Thu, 19 Jun 2008 10:20:56 +0200; ok, thanks for the tip. right now, I'm not able to reproduce the bug anymore. Thanks for the support Dave. BTW, this is the xfs_repair output: Phase 1 - find and verify superblock... Phase 2 - using; /archives/xfs/2008-06/msg00217.html (11,598 bytes)
6. XFS: 2.6.26-rc6 link count mismatch for inode (score: 1): Author: "Marco Berizzi" <pupilla@xxxxxxxxxxx>; Date: Mon, 16 Jun 2008 11:11:31 +0200; 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 un; /archives/xfs/2008-06/msg00623.html (48,848 bytes)
7. Re: XFS: 2.6.26-rc6 link count mismatch for inode (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Thu, 19 Jun 2008 02:12:52 +1000; 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; /archives/xfs/2008-06/msg00659.html (8,972 bytes)
8. Re: XFS: 2.6.26-rc6 link count mismatch for inode (score: 1): Author: "Marco Berizzi" <pupilla@xxxxxxxxxxx>; Date: Wed, 18 Jun 2008 18:39:59 +0200; root@Venus:/etc# cat mtab /dev/sda2 / xfs rw 0 0 root@Venus:/etc# cat fstab /dev/sda2 / xfs defaults 1 1 scsi0 : ahci scsi1 : ahci scsi2 : ahci ata1: SATA max UDMA/133 abar m2048@0xe4809000 port 0xe4; /archives/xfs/2008-06/msg00661.html (11,732 bytes)
9. Re: XFS: 2.6.26-rc6 link count mismatch for inode (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Thu, 19 Jun 2008 14:14:41 +1000; [...] Yeah, it sounds like the I/O subsystem hung somewhere. Without details I can't say what went wrong. If it happens again doing this: To get a dump of all the blocked processes on the console. Th; /archives/xfs/2008-06/msg00667.html (10,653 bytes)
10. Re: XFS: 2.6.26-rc6 link count mismatch for inode (score: 1): Author: "Marco Berizzi" <pupilla@xxxxxxxxxxx>; Date: Thu, 19 Jun 2008 10:20:56 +0200; ok, thanks for the tip. right now, I'm not able to reproduce the bug anymore. Thanks for the support Dave. BTW, this is the xfs_repair output: Phase 1 - find and verify superblock... Phase 2 - using; /archives/xfs/2008-06/msg00677.html (11,598 bytes)
11. XFS: 2.6.26-rc6 link count mismatch for inode (score: 1): Author: "Marco Berizzi" <pupilla@xxxxxxxxxxx>; Date: Mon, 16 Jun 2008 11:11:31 +0200; 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 un; /archives/xfs/2008-06/msg01083.html (48,878 bytes)
12. Re: XFS: 2.6.26-rc6 link count mismatch for inode (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Thu, 19 Jun 2008 02:12:52 +1000; 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; /archives/xfs/2008-06/msg01119.html (9,060 bytes)
13. Re: XFS: 2.6.26-rc6 link count mismatch for inode (score: 1): Author: "Marco Berizzi" <pupilla@xxxxxxxxxxx>; Date: Wed, 18 Jun 2008 18:39:59 +0200; root@Venus:/etc# cat mtab /dev/sda2 / xfs rw 0 0 root@Venus:/etc# cat fstab /dev/sda2 / xfs defaults 1 1 scsi0 : ahci scsi1 : ahci scsi2 : ahci ata1: SATA max UDMA/133 abar m2048@0xe4809000 port 0xe4; /archives/xfs/2008-06/msg01121.html (11,833 bytes)
14. Re: XFS: 2.6.26-rc6 link count mismatch for inode (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Thu, 19 Jun 2008 14:14:41 +1000; [...] Yeah, it sounds like the I/O subsystem hung somewhere. Without details I can't say what went wrong. If it happens again doing this: To get a dump of all the blocked processes on the console. Th; /archives/xfs/2008-06/msg01127.html (10,842 bytes)
15. Re: XFS: 2.6.26-rc6 link count mismatch for inode (score: 1): Author: "Marco Berizzi" <pupilla@xxxxxxxxxxx>; Date: Thu, 19 Jun 2008 10:20:56 +0200; ok, thanks for the tip. right now, I'm not able to reproduce the bug anymore. Thanks for the support Dave. BTW, this is the xfs_repair output: Phase 1 - find and verify superblock... Phase 2 - using; /archives/xfs/2008-06/msg01137.html (11,800 bytes)

Current List: 1 - 15
Page: [1]