Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*xfs\s+i\/O\s+error\s*$/: 43 ]

Total 43 documents matching your query.

1. xfs I/O error (score: 1)
Author: Rekrutacja119 <rekrutacja119@xxxxxxxxx>
Date: Sat, 23 Feb 2008 22:46:52 +0100
hello, is there any way to force XFS to ignore I/O errors? it seems it is shutting down the fs when it encounters any error. The problem is that i can't mark badsectors, as XFS doesn't support bad se
/archives/xfs/2008-02/msg00313.html (9,842 bytes)

2. Fwd: xfs I/O error (score: 1)
Author: Rekrutacja119 <rekrutacja119@xxxxxxxxx>
Date: Sat, 23 Feb 2008 23:00:29 +0100
one more thing, i got it from logs when the XFS got down: Feb 23 22:58:20 debian kernel: [<c021f67e>] xfs_free_ag_extent+0x49e/0x750 Feb 23 22:58:20 debian kernel: [<c0221270>] xfs_free_extent+0xe0/0
/archives/xfs/2008-02/msg00314.html (12,495 bytes)

3. Re: xfs I/O error (score: 1)
Author: Iustin Pop <iusty@xxxxxxxxx>
Date: Sat, 23 Feb 2008 23:08:18 +0100
I'm not really sure, but the above seems wrong. badblocks has a default block size of 1024 (-c does something else, not set the block size), and you use that block number as an offset in bytes for dd
/archives/xfs/2008-02/msg00315.html (10,087 bytes)

4. Re: xfs I/O error (score: 1)
Author: Rekrutacja119 <rekrutacja119@xxxxxxxxx>
Date: Sat, 23 Feb 2008 23:14:32 +0100
so i should use the list i got from badblocks with dd but with bs=1024? are you sure? i'm not sure what is my block size, but xfs_info says this: debian:/# xfs_info /dev/md0 meta-data=/dev/md0 isize=
/archives/xfs/2008-02/msg00316.html (12,404 bytes)

5. Re: xfs I/O error (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Sat, 23 Feb 2008 21:53:28 -0600
It does not shut down on any error; it should only be shutting down on errors after which it cannot guarantee filesystem consistency. Depends on what the sector is and what xfs is doing with it. xfs
/archives/xfs/2008-02/msg00318.html (11,453 bytes)

6. Re: xfs I/O error (score: 1)
Author: Iustin Pop <iusty@xxxxxxxxx>
Date: Sun, 24 Feb 2008 10:01:06 +0100
the block size of the filesystem has no relation to the block size badblocks uses in checking the block device. [...] I don't understand what do you want to do with smartctl at all. How would offlini
/archives/xfs/2008-02/msg00319.html (9,869 bytes)

7. Re: xfs I/O error (score: 1)
Author: Rekrutacja119 <rekrutacja119@xxxxxxxxx>
Date: Sun, 24 Feb 2008 12:52:38 +0100
smartctl -t offline is i think scheduling a SMART test i will try what you say, but there is no way to force XFS to not unmount filesystem if it finds out I/O error? also, i didnt edit any info, it w
/archives/xfs/2008-02/msg00323.html (11,340 bytes)

8. Re: xfs I/O error (score: 1)
Author: Ragnar Kj°rstad <xfs@xxxxxxxxxxxxxxxxxxx
Date: Sun, 24 Feb 2008 13:17:23 +0100
If you really wanted to you could probably use dm to map your bad sectors to another device. -- Ragnar Kj°rstad Software Engineer Platform Computin
/archives/xfs/2008-02/msg00324.html (8,453 bytes)

9. Re: xfs I/O error (score: 1)
Author: Iustin Pop <iusty@xxxxxxxxx>
Date: Sun, 24 Feb 2008 13:31:29 +0100
ah yes, you're right, I'm sorry. I would recommend to use not -t offline but -t long - AFAIK, the 'offline' test just updates the attributes but not scan the whole of the disk. In any case, I don't t
/archives/xfs/2008-02/msg00325.html (9,340 bytes)

10. Re: xfs I/O error (score: 1)
Author: Rekrutacja119 <rekrutacja119@xxxxxxxxx>
Date: Mon, 25 Feb 2008 17:40:27 +0100
i tried doing dd if with the bs=1024, and the dd command went fine! i really don't understand it :( i wont write zeros to it, if it is fine, since this sector is probably correct. any ideas what to d
/archives/xfs/2008-02/msg00346.html (10,467 bytes)

11. Re: xfs I/O error (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Mon, 25 Feb 2008 11:17:48 -0600
mount it readonly. xfs isn't going to continue if doing so would further corrupt the fs. -Eric
/archives/xfs/2008-02/msg00348.html (9,471 bytes)

12. Re: xfs I/O error (score: 1)
Author: Rekrutacja119 <rekrutacja119@xxxxxxxxx>
Date: Tue, 26 Feb 2008 21:13:07 +0100
2008/2/25, Ragnar Kj°rstad <xfs@xxxxxxxxxxxxxxxxxxx>: but i suppose i can do it like Eric told me - mount it read only. effects would be the same - i will have acess to everything that is readable
/archives/xfs/2008-02/msg00374.html (10,849 bytes)

13. xfs I/O error (score: 1)
Author: Rekrutacja119 <rekrutacja119@xxxxxxxxx>
Date: Sat, 23 Feb 2008 22:46:52 +0100
hello, is there any way to force XFS to ignore I/O errors? it seems it is shutting down the fs when it encounters any error. The problem is that i can't mark badsectors, as XFS doesn't support bad se
/archives/xfs/2008-02/msg00729.html (9,842 bytes)

14. Fwd: xfs I/O error (score: 1)
Author: Rekrutacja119 <rekrutacja119@xxxxxxxxx>
Date: Sat, 23 Feb 2008 23:00:29 +0100
one more thing, i got it from logs when the XFS got down: Feb 23 22:58:20 debian kernel: [<c021f67e>] xfs_free_ag_extent+0x49e/0x750 Feb 23 22:58:20 debian kernel: [<c0221270>] xfs_free_extent+0xe0/0
/archives/xfs/2008-02/msg00730.html (12,495 bytes)

15. Re: xfs I/O error (score: 1)
Author: Iustin Pop <iusty@xxxxxxxxx>
Date: Sat, 23 Feb 2008 23:08:18 +0100
I'm not really sure, but the above seems wrong. badblocks has a default block size of 1024 (-c does something else, not set the block size), and you use that block number as an offset in bytes for dd
/archives/xfs/2008-02/msg00731.html (10,087 bytes)

16. Re: xfs I/O error (score: 1)
Author: Rekrutacja119 <rekrutacja119@xxxxxxxxx>
Date: Sat, 23 Feb 2008 23:14:32 +0100
so i should use the list i got from badblocks with dd but with bs=1024? are you sure? i'm not sure what is my block size, but xfs_info says this: debian:/# xfs_info /dev/md0 meta-data=/dev/md0 isize=
/archives/xfs/2008-02/msg00732.html (12,404 bytes)

17. Re: xfs I/O error (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Sat, 23 Feb 2008 21:53:28 -0600
It does not shut down on any error; it should only be shutting down on errors after which it cannot guarantee filesystem consistency. Depends on what the sector is and what xfs is doing with it. xfs
/archives/xfs/2008-02/msg00734.html (11,453 bytes)

18. Re: xfs I/O error (score: 1)
Author: Iustin Pop <iusty@xxxxxxxxx>
Date: Sun, 24 Feb 2008 10:01:06 +0100
the block size of the filesystem has no relation to the block size badblocks uses in checking the block device. [...] I don't understand what do you want to do with smartctl at all. How would offlini
/archives/xfs/2008-02/msg00735.html (9,869 bytes)

19. Re: xfs I/O error (score: 1)
Author: Rekrutacja119 <rekrutacja119@xxxxxxxxx>
Date: Sun, 24 Feb 2008 12:52:38 +0100
smartctl -t offline is i think scheduling a SMART test i will try what you say, but there is no way to force XFS to not unmount filesystem if it finds out I/O error? also, i didnt edit any info, it w
/archives/xfs/2008-02/msg00739.html (11,340 bytes)

20. Re: xfs I/O error (score: 1)
Author: Ragnar Kj°rstad <xfs@xxxxxxxxxxxxxxxxxxx
Date: Sun, 24 Feb 2008 13:17:23 +0100
If you really wanted to you could probably use dm to map your bad sectors to another device. -- Ragnar Kj°rstad Software Engineer Platform Computin
/archives/xfs/2008-02/msg00740.html (8,453 bytes)


This search system is powered by Namazu