error on my LUNS

shafey · 07-15-2012, 05:14 AM

Dear All
I am running HP EVA 8000 with RHEL 5.7 (Lun Size 6.7 T )

The problem i face many times recently File system error at my Luns /dev/mapper/Linux-Lun (/dev/sdb , /dev/sdh/ ,/dev/sde /dev/sdj)

My Question is :
Is there any way to make file system check on just one subsystem like

check /dev/sdb "because if i will check my Lun it will take too long time"

Regards

rmugunthan · 07-16-2012, 12:54 AM

Hi,

Could you explain "/dev/sdb, /dev/sdh/, /dev/sde and /dev/sdj" are different paths of your single LUN (multipathing) or seperate LUNS?

shafey · 07-16-2012, 04:51 AM

Single Lun "multipathing"
and i am using LVM (command line ) to create LV

grim76 · 07-16-2012, 10:34 AM

Ok so you have a single lun, but multiple paths back to the storage. If these are all the same multipath device then the entire file system will need to be checked.

anomie · 07-16-2012, 05:45 PM

What "file system errors" are you seeing, exactly? Please copy/paste and use code tags.

shafey · 07-17-2012, 04:56 AM

here is my errors

Quote:

EXT3-fs error (device dm-35): ext3_free_blocks: Freeing blocks not in datazone - block = 3338527582, count = 1
EXT3-fs error (device dm-35): ext3_free_blocks: Freeing blocks not in datazone - block = 3526055329, count = 1
EXT3-fs error (device dm-35): ext3_free_blocks: Freeing blocks not in datazone - block = 1977396702, count = 1
EXT3-fs error (device dm-35): ext3_free_blocks: Freeing blocks not in datazone - block = 2635050982, count = 1
EXT3-fs error (device dm-35): ext3_free_blocks: Freeing blocks not in datazone - block = 2423519485, count = 1
EXT3-fs error (device dm-35) in ext3_free_blocks_sb: Journal has aborted
EXT3-fs error (device dm-35): ext3_free_blocks: Freeing blocks not in datazone - block = 2957352573, count = 1
EXT3-fs error (device dm-35) in ext3_free_blocks_sb: Journal has aborted
EXT3-fs error (device dm-35) in ext3_free_blocks_sb: Journal has aborted
EXT3-fs error (device dm-35): ext3_free_blocks: Freeing blocks not in datazone - block = 3700142503, count = 1
EXT3-fs error (device dm-35) in ext3_free_blocks_sb: Journal has aborted
EXT3-fs error (device dm-35) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device dm-35) in ext3_truncate: Journal has aborted
EXT3-fs error (device dm-35) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device dm-35) in ext3_orphan_del: Journal has aborted
EXT3-fs error (device dm-35) in ext3_reserve_inode_write: Journal has aborted
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
ext3_abort called.
EXT3-fs error (device dm-35): ext3_put_super: Couldn't clean up the journal
kjournald starting. Commit interval 5 seconds
EXT3-fs warning (device dm-35): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure
EXT3-fs warning (device dm-35): ext3_clear_journal_err: Marking fs in need of filesystem check.
EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
EXT3 FS on dm-35, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.

Quote:

Jul 15 01:20:28 ASIRAVI42 last message repeated 16 times
Jul 15 01:20:28 ASIRAVI42 last message repeated 5 times
Jul 15 03:57:07 ASIRAVI42 kernel: EXT3-fs error (device dm-35): ext3_lookup: unlinked inode 438484993 in dir #209338403
Jul 15 03:57:41 ASIRAVI42 kernel: EXT3-fs error (device dm-35): ext3_lookup: unlinked inode 438484993 in dir #209338403
Jul 15 04:02:33 ASIRAVI42 rhsmd: This system is missing one or more valid entitlement certificates. Please run subscription-manager for more information.
Jul 15 04:09:06 ASIRAVI42 kernel: EXT3-fs error (device dm-35): ext3_lookup: unlinked inode 438484993 in dir #209338403
Jul 15 04:21:19 ASIRAVI42 kernel: EXT3-fs error (device dm-35): ext3_lookup: unlinked inode 438484993 in dir #209338403
Jul 15 04:33:06 ASIRAVI42 kernel: EXT3-fs error (device dm-35): ext3_lookup: unlinked inode 438484993 in dir #209338403
Jul 15 04:45:05 ASIRAVI42 kernel: EXT3-fs error (device dm-35): ext3_lookup: unlinked inode 438484993 in dir #209338403
Jul 15 04:57:06 ASIRAVI42 kernel: EXT3-fs error (device dm-35): ext3_lookup: unlinked inode 438484993 in dir #209338403
Jul 15 05:09:41 ASIRAVI42 kernel: EXT3-fs error (device dm-35): ext3_lookup: unlinked inode 438484993 in dir #209338403
Jul 15 05:19:00 ASIRAVI42 kernel: EXT3-fs error (device dm-35): ext3_lookup: unlinked inode 433012907 in dir #433012759
Jul 15 05:19:07 ASIRAVI42 last message repeated 9 times
Jul 15 05:19:09 ASIRAVI42 kernel: EXT3-fs error (device dm-35): ext3_lookup: unlinked inode 433012926 in dir #433012759
Jul 15 05:21:06 ASIRAVI42 kernel: printk: 1 messages suppressed.
Jul 15 05:21:06 ASIRAVI42 kernel: EXT3-fs error (device dm-35): ext3_lookup: unlinked inode 438484993 in dir #209338403
Jul 15 05:33:05 ASIRAVI42 kernel: EXT3-fs error (device dm-35): ext3_lookup: unlinked inode 438484993 in dir #209338403
Jul 15 05:45:33 ASIRAVI42 kernel: EXT3-fs error (device dm-35): ext3_lookup: unlinked inode 438484993 in dir #209338403
Jul 15 05:57:06 ASIRAVI42 kernel: EXT3-fs error (device dm-35): ext3_lookup: unlinked inode 438484993 in dir #209338403
Jul 15 06:09:13 ASIRAVI42 kernel: EXT3-fs error (device dm-35): ext3_lookup: unlinked inode 438484993 in dir #209338403
Jul 15 06:12:05 ASIRAVI42 kernel: EXT3-fs error (device dm-35): ext3_lookup: unlinked inode 438484993 in dir #209338403
Jul 15 06:24:07 ASIRAVI42 kernel: EXT3-fs error (device dm-35): ext3_lookup: unlinked inode 438484993 in dir #209338403
Jul 15 06:36:10 ASIRAVI42 kernel: EXT3-fs error (device dm-35): ext3_lookup: unlinked inode 438484993 in dir #209338403
Jul 15 06:48:06 ASIRAVI42 kernel: EXT3-fs error (device dm-35): ext3_lookup: unlinked inode 438484993 in dir #209338403
Jul 15 07:00:18 ASIRAVI42 kernel: EXT3-fs error (device dm-35): ext3_lookup: unlinked inode 438484993 in dir #209338403
Jul 15 07:12:07 ASIRAVI42 kernel: EXT3-fs error (device dm-35): ext3_lookup: unlinked inode 438484993 in dir #209338403
Jul 15 07:24:07 ASIRAVI42 kernel: EXT3-fs error (device dm-35): ext3_lookup: unlinked inode 438484993 in dir #209338403
Jul 15 07:27:16 ASIRAVI42 kernel: EXT3-fs error (device dm-35): ext3_lookup: unlinked inode 438484993 in dir #209338403
Jul 15 07:39:06 ASIRAVI42 kernel: EXT3-fs error (device dm-35): ext3_lookup: unlinked inode 438484993 in dir #209338403
Jul 15 07:51:24 ASIRAVI42 kernel: EXT3-fs error (device dm-35): ext3_lookup: unlinked inode 438484993 in dir #209338403
Jul 15 08:03:08 ASIRAVI42 kernel: EXT3-fs error (device dm-35): ext3_lookup: unlinked inode 438484993 in dir #209338403
Jul 15 08:15:06 ASIRAVI42 kernel: EXT3-fs error (device dm-35): ext3_lookup: unlinked inode 438484993 in dir #209338403
Jul 15 08:19:34 ASIRAVI42 kernel: EXT3-fs error (device dm-35): ext3_lookup: unlinked inode 433012921 in dir #433012780

anomie · 07-17-2012, 05:03 PM

Ouch! Yes, plan a downtime and run the fsck(8).

I was just checking to be sure you weren't seeing the usual flurry of various (harmless) errors reported by RHEL systems on LUNs that haven't been partitioned.

Another question for you: are you accessing the LUN from only this host? Or multiple hosts?

shafey · 07-18-2012, 01:29 AM

no just from that host (One host )

Is there another solution

Because for scan that lun 6.7 T takes very long time

anomie · 07-18-2012, 01:34 PM

Absolutely not. Bite the bullet, plan a downtime, and do a fsck(8). The longer you wait on this - with a live filesystem - the more risk you're putting your current data and future writes in.

edit: I shouldn't have to say this, but will anyway: ensure you have a good filesystem backup before proceeding.