xfs
[Top] [All Lists]

Fwd: xfs I/O error

To: xfs@xxxxxxxxxxx
Subject: Fwd: xfs I/O error
From: Rekrutacja119 <rekrutacja119@xxxxxxxxx>
Date: Sat, 23 Feb 2008 23:00:29 +0100
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=3QQt4bb5WoZIVo/3UXk7dH9Bd2jG6xzO5CzYv3PfsxI=; b=d7jH2a1BxkjTnXDay+pceqWkUt9p4L4RRr9Vvq3LOFWQlnVFAoGW8pVLyEI8zIIpEZ641QdC8PzbR9MpjkBl0dr2VKBGJsNywcyjyhmEv/aRzNQW2jUSAeXXe+88IUGwp4BbH0dH4LuRhPZ4Nbi7OUmPiAujEFKG/eebuQ3Zy2w=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=Ns7/5o8ndD82FZAOESzLw4k/ZhIFjloZkiS7ZSi0po8Nmv4d4Iaxnz2N8ms7dG0Cft/wgbFQrD+jdHx3lpvTeoMmtp6i8xUfz7yfWUNqWKAnCNaM/LA84vD6cwbtK2ow/NBC6ereoS73qgj1SxDDGPwG5+gB8ytZtBT7z6Q6voI=
In-reply-to: <2db2c6b80802231346r78d59381j49927e15f40e7ef8@xxxxxxxxxxxxxx>
References: <2db2c6b80802231346r78d59381j49927e15f40e7ef8@xxxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
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/0x110
Feb 23 22:58:20 debian kernel: [<c0221270>] xfs_free_extent+0xe0/0x110
Feb 23 22:58:20 debian kernel: [<c025d24c>] xlog_grant_push_ail+0x3c/0x140
Feb 23 22:58:20 debian kernel: [<c022c1fa>] xfs_bmap_finish+0x13a/0x190
Feb 23 22:58:20 debian kernel: [<c0236730>] xfs_bunmapi+0x0/0xfb0
Feb 23 22:58:20 debian kernel: [<c025442a>] xfs_itruncate_finish+0x27a/0x400
Feb 23 22:58:20 debian kernel: [<c0276b3c>] xfs_inactive+0x49c/0x510
Feb 23 22:58:20 debian kernel: [<c0282697>] xfs_fs_clear_inode+0x77/0xc0
Feb 23 22:58:20 debian kernel: [<c017976f>] clear_inode+0x8f/0x140
Feb 23 22:58:20 debian kernel: [<c014f827>] truncate_inode_pages+0x17/0x20
Feb 23 22:58:20 debian kernel: [<c017990d>] generic_delete_inode+0xed/0x100
Feb 23 22:58:20 debian kernel: [<c0178f4c>] iput+0x5c/0x70
Feb 23 22:58:20 debian kernel: [<c017052f>] do_unlinkat+0xef/0x150
Feb 23 22:58:20 debian kernel: [<c0102972>] sysenter_past_esp+0x5f/0x85
Feb 23 22:58:20 debian kernel: [<c0390000>] nf_nat_ftp+0xd0/0x100
Feb 23 22:58:20 debian kernel: =======================
Feb 23 22:58:20 debian kernel: xfs_force_shutdown(md0,0x8) called from line
4258 of file fs/xfs/xfs_bmap.c.  Return address = 0xc02830bc


please, can i change it somehow? i'm so desperate i think i will try to
change this line in kernel, no matter what consequences it might have (if i
don't allow access to this disk right away, i might as well delete the whole
thing, so it's very important)

also, xfs_repair stops on :

cannot read inode 44610144, disk block 22305072, cnt 16


---------- Forwarded message ----------
From: Rekrutacja119 <rekrutacja119@xxxxxxxxx>
Date: 23-02-2008 22:46
Subject: xfs I/O error
To: xfs@xxxxxxxxxxx


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
sector marking, but i also cannot access any correct data on partition,
because when i try to access damaged sector, the whole fs goes down.

any idea why?

i use xfsprogs 2.9.4, my xfs is array made from 3 HDs, RAID 0, and one of
them is getting some bad sectors. i cannot replace it currently.

after i run xfs_repair on it, i was able to mount it and access the data,
but when somebody tries to access bad data, the whole XFS goes down. i don't
want that, i also dont have place to xfsmetadump the whole array to another
disks.

i tried scaning whole disk with badblocks (badblocks -c 1 -s -v /dev/sdb),
and then running dd if=/dev/zero of=/dev/sdb count=1 bs=1
seek=NUMBER_FROM_BADBLOCKOUTPUT

but every block was written fine! (which is strange i guess), and it didnt
help.

please advise me anything other than switching the drive (i will do it,
can't now though) or dumping the whole thing as i need to much space.

the easiest solution would be to just ignore errors, and if not, then to
somehow force xfs to mark them as bad sectors (smartctl is showing errors
like for example

# 2  Extended offline    Completed: unknown failure    90%      9395
-

or


Error 8324 occurred at disk power-on lifetime: 9398 hours (391 days + 14
hours)
  When the command that caused the error occurred, the device was active or
idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 30 33 59 e6  Error: UNC at LBA = 0x06593330 = 106509104


[[HTML alternate version deleted]]


<Prev in Thread] Current Thread [Next in Thread>