Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*XFS\s+internal\s+error\s+when\s+NFS\s+client\s+accesses\s+nonexistent\s+inode\s*$/: 18 ]

Total 18 documents matching your query.

1. Re: XFS internal error when NFS client accesses nonexistent inode (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Thu, 1 Jan 2009 12:14:09 -0500
This is: di_ok = be16_to_cpu(dip->di_core.di_magic) == XFS_DINODE_GOOD_VERSION(dip->di_core.di_version); if (unlikely(XFS_TEST_ERROR(!di_ok, mp, XFS_ERRTAG_ITOBP_INOTOBP, XFS_RANDOM_ITOBP_INOTOBP)))
/archives/xfs/2009-01/msg00002.html (10,117 bytes)

2. Re: XFS internal error when NFS client accesses nonexistent inode (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Thu, 1 Jan 2009 12:37:56 -0500
This should cure your shutdowns on a 2.6.27-ish codebase: Index: btrfs-unstable/fs/xfs/linux-2.6/xfs_export.c == -- btrfs-unstable.orig/fs/xfs/linux-2.6/xfs_export.c 2009-01-01 18:34:39.868671500 +01
/archives/xfs/2009-01/msg00004.html (8,572 bytes)

3. Re: XFS internal error when NFS client accesses nonexistent inode (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Thu, 1 Jan 2009 14:00:39 -0500
Btw, you update /proc/sys/fs/xfs/error_level manually? The corruption test only triggers from a avalue of 5, but 3 is the default.
/archives/xfs/2009-01/msg00008.html (7,945 bytes)

4. Re: XFS internal error when NFS client accesses nonexistent inode (score: 1)
Author: Mario Becroft <mb@xxxxxxxxxxxxx>
Date: Fri, 02 Jan 2009 12:15:46 +1300
I was getting: Dec 31 09:12:46 nfs1 kernel: nfsd: non-standard errno: -117 and in trying to figure out what it meant, I bumped up the XFS debug level to 6, which enabled me to see the errors from XFS
/archives/xfs/2009-01/msg00026.html (9,241 bytes)

5. Re: XFS internal error when NFS client accesses nonexistent inode (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Thu, 1 Jan 2009 18:20:16 -0500
Looking at the code again there indeed aren't shutdowns, just stacktraces. So yes, the stacktraces are caused by the higher error level. With debug kernels it's still a kernel crash though, but no on
/archives/xfs/2009-01/msg00027.html (9,713 bytes)

6. broken? (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Thu, 1 Jan 2009 12:14:09 -0500
h CONFIG_LBD=n on x86, but the following patch should fix it: Index: linux-2.6/fs/xfs/xfs_btree.c == -- linux-2.6.orig/fs/xfs/xfs_btree.c 2009-01-01 15:57:04.606547140
/archives/xfs/2009-01/msg00276.html (10,117 bytes)

7. sses nonexistent inode (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Thu, 1 Jan 2009 12:37:56 -0500
ng_Support That's very hard to do, given that inode numbers encode the location on disk. To support your NFS exporting scenario you would also have to preserve the gen
/archives/xfs/2009-01/msg00278.html (8,572 bytes)

8. CH] xfsprogs: make install-qa should only install additional headers (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Thu, 1 Jan 2009 14:00:39 -0500
headers you need for qa and it doesn't, it only (now) installs the extras right...? By itself it's kind of a useless t
/archives/xfs/2009-01/msg00282.html (7,945 bytes)

9. (score: 1)
Author: Mario Becroft <mb@xxxxxxxxxxxxx>
Date: Fri, 02 Jan 2009 12:15:46 +1300
def HAVE_FORMAT32, but this is never defined anywhere so it is always the default behavior; just remove the ifndef goop. Signed-off-by: Eric Sandeen <sandeen@xxxxxxxxx
/archives/xfs/2009-01/msg00300.html (9,241 bytes)

10. move always-true #ifndef HAVE_FORMAT32 tests (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Thu, 1 Jan 2009 18:20:16 -0500
fs1 kernel: nfsd: non-standard errno: -117 and in trying to figure out what it meant, I bumped up the XFS debug level to 6, which enabled me to see the errors from XFS
/archives/xfs/2009-01/msg00301.html (9,713 bytes)

11. XFS internal error when NFS client accesses nonexistent inode (score: 1)
Author: Mario Becroft <mb@xxxxxxxxxxxxx>
Date: Thu, 01 Jan 2009 03:09:08 +1300
/archives/xfs/2008-12/msg00614.html (13,609 bytes)

12. XFS internal error when NFS client accesses nonexistent inode (score: 1)
Author: Mario Becroft <mb@xxxxxxxxxxxxx>
Date: Thu, 01 Jan 2009 03:09:08 +1300
.
/archives/xfs/2008-12/msg01231.html (13,609 bytes)

13. Re: XFS internal error when NFS client accesses nonexistent inode (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Thu, 1 Jan 2009 12:14:09 -0500
This is: di_ok = be16_to_cpu(dip->di_core.di_magic) == XFS_DINODE_GOOD_VERSION(dip->di_core.di_version); if (unlikely(XFS_TEST_ERROR(!di_ok, mp, XFS_ERRTAG_ITOBP_INOTOBP, XFS_RANDOM_ITOBP_INOTOBP)))
/archives/xfs/2009-01/msg00652.html (10,217 bytes)

14. Re: XFS internal error when NFS client accesses nonexistent inode (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Thu, 1 Jan 2009 12:37:56 -0500
This should cure your shutdowns on a 2.6.27-ish codebase: Index: btrfs-unstable/fs/xfs/linux-2.6/xfs_export.c == -- btrfs-unstable.orig/fs/xfs/linux-2.6/xfs_export.c 2009-01-01 18:34:39.868671500 +01
/archives/xfs/2009-01/msg00654.html (8,682 bytes)

15. Re: XFS internal error when NFS client accesses nonexistent inode (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Thu, 1 Jan 2009 14:00:39 -0500
Btw, you update /proc/sys/fs/xfs/error_level manually? The corruption test only triggers from a avalue of 5, but 3 is the default.
/archives/xfs/2009-01/msg00658.html (8,055 bytes)

16. Re: XFS internal error when NFS client accesses nonexistent inode (score: 1)
Author: Mario Becroft <mb@xxxxxxxxxxxxx>
Date: Fri, 02 Jan 2009 12:15:46 +1300
I was getting: Dec 31 09:12:46 nfs1 kernel: nfsd: non-standard errno: -117 and in trying to figure out what it meant, I bumped up the XFS debug level to 6, which enabled me to see the errors from XFS
/archives/xfs/2009-01/msg00676.html (9,381 bytes)

17. Re: XFS internal error when NFS client accesses nonexistent inode (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Thu, 1 Jan 2009 18:20:16 -0500
Looking at the code again there indeed aren't shutdowns, just stacktraces. So yes, the stacktraces are caused by the higher error level. With debug kernels it's still a kernel crash though, but no on
/archives/xfs/2009-01/msg00677.html (9,867 bytes)

18. XFS internal error when NFS client accesses nonexistent inode (score: 1)
Author: Mario Becroft <mb@xxxxxxxxxxxxx>
Date: Thu, 01 Jan 2009 03:09:08 +1300
I hit a seemingly strange problem today when I xfsdump/restored some filesystems from one volume onto another. When I exported the new volumes, errors like the following started to occur: Dec 31 09:1
/archives/xfs/2008-12/msg01848.html (13,609 bytes)


This search system is powered by Namazu