Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Large\s+file\s+I\/O\s+error\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Large\s+file\s+I\/O\s+error\s*$/: 24 ]

Total 24 documents matching your query.

1. ver oops ..... any ideas. (score: 1): Author: xxxxxxxxxx>; Date: Thu, 17 Jan 2002 20:08:44 +0100; I think tripped over a nice, juicy bug here. I used ftruncate64() to create a sparse file of 2^63 bytes. Then I run mkfs.xfs on it (without any options). The filesystem on which the large file resid; /archives/xfs/2002-01/msg00466.html (7,977 bytes)
2. eas. (score: 1): Author: xxxxxxxxxx>; Date: Thu, 17 Jan 2002 20:09:49 +0100; I forgot to mention: Linux bzzrt 2.4.17-xfs #1 Fri Jan 11 16:48:32 CET 2002 i686 unknown -- Wessel Dankers <wsl@xxxxxxxxxxxx> Budget cuts; /archives/xfs/2002-01/msg00467.html (7,741 bytes)
3. (score: 1): Author: xxxxxxxxxx>; Date: 17 Jan 2002 13:13:04 -0600; Someone else just pointed out that forced shutdown is overwriting the super block - which is not good. There appear to be a bunch of dirty buffers with a zero disk address in them left behind. It is; /archives/xfs/2002-01/msg00468.html (9,208 bytes)
4. (score: 1): Author: rd@xxxxxxx>; Date: Thu, 17 Jan 2002 20:31:46 +0100; Ok, great! Any idea what's causing the forced shutdown in the first place, though? -- Wessel Dankers <wsl@xxxxxxxxxxxx> Borg nanites have infested the server; /archives/xfs/2002-01/msg00469.html (8,277 bytes)
5. (score: 1): Author: xxxxxxxxxx>; Date: 17 Jan 2002 13:35:10 -0600; Buffered I/O beyond 2^44 bytes into the sparse file probably. There is a hole in the code here. The linux VM uses a 32 bit page number index to index cache data. So 2^32 * 4096 is as bit as you can g; /archives/xfs/2002-01/msg00470.html (8,869 bytes)
6. erworks XFS introduction. (score: 1): Author: in@xxxxxxx>; Date: Thu, 17 Jan 2002 21:09:00 +0100 (CET); Just have to say that I can confirm this, I had to run xfs_repair after a forced shutdown because of major interruptproblems in the machine so the promise ata-driver complained about irq timeouts all; /archives/xfs/2002-01/msg00472.html (8,505 bytes)
7. (score: 1): Author: xxxxxxxxxx>; Date: 17 Jan 2002 14:15:24 -0600; The problem we have found would probably only affect the superblock. Delalloc buffer heads have bh->b_blocknr==0, (since no disk block has yet been assigned) but we were incorrectly clearing the dela; /archives/xfs/2002-01/msg00473.html (8,722 bytes)
8. (score: 1): Author: en@xxxxxxx>; Date: Thu, 17 Jan 2002 21:35:03 +0100; Ack. If I create the file to be exactly 2^44 bytes the problem goes away. (mkfs fails though, ENOSPC ;) The downside is that any user can cause a forced shutdown which is a bit worrisome from a secur; /archives/xfs/2002-01/msg00474.html (9,250 bytes)
9. ne - was: Re: XFS is innocen t (score: 1): Author: y <I.D.Hardy@xxxxxxxxxxx>; Date: Thu, 17 Jan 2002 20:08:44 +0100; I think tripped over a nice, juicy bug here. I used ftruncate64() to create a sparse file of 2^63 bytes. Then I run mkfs.xfs on it (without any options). The filesystem on which the large file resid; /archives/xfs/2002-01/msg01395.html (7,977 bytes)
10. innocen t (score: 1): Author: ankers <wsl@xxxxxxxxxxxx>; Date: Thu, 17 Jan 2002 20:09:49 +0100; I forgot to mention: Linux bzzrt 2.4.17-xfs #1 Fri Jan 11 16:48:32 CET 2002 i686 unknown -- Wessel Dankers <wsl@xxxxxxxxxxxx> Budget cuts; /archives/xfs/2002-01/msg01396.html (7,741 bytes)
11. ver oops ..... any ideas. (score: 1): Author: ankers <wsl@xxxxxxxxxxxx>; Date: 17 Jan 2002 13:13:04 -0600; Someone else just pointed out that forced shutdown is overwriting the super block - which is not good. There appear to be a bunch of dirty buffers with a zero disk address in them left behind. It is; /archives/xfs/2002-01/msg01397.html (9,208 bytes)
12. (score: 1): Author: Steve Lord <lord@xxxxxxx>; Date: Thu, 17 Jan 2002 20:31:46 +0100; Ok, great! Any idea what's causing the forced shutdown in the first place, though? -- Wessel Dankers <wsl@xxxxxxxxxxxx> Borg nanites have infested the server; /archives/xfs/2002-01/msg01398.html (8,277 bytes)
13. Large file I/O error (score: 1): Author: ankers <wsl@xxxxxxxxxxxx>; Date: 17 Jan 2002 13:35:10 -0600; Buffered I/O beyond 2^44 bytes into the sparse file probably. There is a hole in the code here. The linux VM uses a 32 bit page number index to index cache data. So 2^32 * 4096 is as bit as you can g; /archives/xfs/2002-01/msg01399.html (8,869 bytes)
14. I/O error (score: 1): Author: n Andrei <florin@xxxxxxx>; Date: Thu, 17 Jan 2002 21:09:00 +0100 (CET); Just have to say that I can confirm this, I had to run xfs_repair after a forced shutdown because of major interruptproblems in the machine so the promise ata-driver complained about irq timeouts all; /archives/xfs/2002-01/msg01401.html (8,505 bytes)
15. I/O error (score: 1): Author: <gandalf@xxxxxxxxxxxxxx>; Date: 17 Jan 2002 14:15:24 -0600; The problem we have found would probably only affect the superblock. Delalloc buffer heads have bh->b_blocknr==0, (since no disk block has yet been assigned) but we were incorrectly clearing the dela; /archives/xfs/2002-01/msg01402.html (8,722 bytes)
16. rks XFS introduction. (score: 1): Author: Sandeen <sandeen@xxxxxxx>; Date: Thu, 17 Jan 2002 21:35:03 +0100; Ack. If I create the file to be exactly 2^44 bytes the problem goes away. (mkfs fails though, ENOSPC ;) The downside is that any user can cause a forced shutdown which is a bit worrisome from a secur; /archives/xfs/2002-01/msg01403.html (9,250 bytes)
17. Large file I/O error (score: 1): Author: Wessel Dankers <wsl@xxxxxxxxxxxx>; Date: Thu, 17 Jan 2002 20:08:44 +0100; oi! I think tripped over a nice, juicy bug here. I used ftruncate64() to create a sparse file of 2^63 bytes. Then I run mkfs.xfs on it (without any options). The filesystem on which the large file re; /archives/xfs/2002-01/msg02324.html (7,977 bytes)
18. Re: Large file I/O error (score: 1): Author: Wessel Dankers <wsl@xxxxxxxxxxxx>; Date: Thu, 17 Jan 2002 20:09:49 +0100; I forgot to mention: Linux bzzrt 2.4.17-xfs #1 Fri Jan 11 16:48:32 CET 2002 i686 unknown -- Wessel Dankers <wsl@xxxxxxxxxxxx> Budget cuts; /archives/xfs/2002-01/msg02325.html (7,838 bytes)
19. Re: Large file I/O error (score: 1): Author: Steve Lord <lord@xxxxxxx>; Date: 17 Jan 2002 13:13:04 -0600; Someone else just pointed out that forced shutdown is overwriting the super block - which is not good. There appear to be a bunch of dirty buffers with a zero disk address in them left behind. It is; /archives/xfs/2002-01/msg02326.html (9,266 bytes)
20. Re: Large file I/O error (score: 1): Author: Wessel Dankers <wsl@xxxxxxxxxxxx>; Date: Thu, 17 Jan 2002 20:31:46 +0100; Ok, great! Any idea what's causing the forced shutdown in the first place, though? -- Wessel Dankers <wsl@xxxxxxxxxxxx> Borg nanites have infested the server; /archives/xfs/2002-01/msg02327.html (8,414 bytes)

Current List: 1 - 20
Page: [1] [2]