"Attempt to access beyond end of device" problem

Yamin, Yossi yamin_yossi at diligent.com
Wed Jun 25 12:55:24 UTC 2008


Hi,

We are using Ext3 on with RedHat 4 U3 File Sysetm.

We got the following errors at the /var/log/messages file

 

Jun 23 09:28:29 diligent1 kernel: attempt to access beyond end of device

Jun 23 09:28:29 diligent1 kernel: sddlmbj1: rw=1, want=6332971392,
limit=4183807887

--

Jun 23 09:37:47 diligent1 kernel: lpfc1: BUFF seg 5 free 946 numblks
1024

Jun 23 09:44:03 diligent1 kernel: attempt to access beyond end of device

Jun 23 09:44:03 diligent1 kernel: sddlmbj1: rw=1, want=6332971392,
limit=4183807887

Jun 23 09:44:03 diligent1 kernel: attempt to access beyond end of device

Jun 23 09:44:03 diligent1 kernel: sddlmbj1: rw=1, want=6332971392,
limit=4183807887

Jun 23 09:44:03 diligent1 kernel: attempt to access beyond end of device

Jun 23 09:44:03 diligent1 kernel: sddlmbj1: rw=1, want=6332971392,
limit=4183807887

Jun 23 09:44:03 diligent1 kernel: attempt to access beyond end of device

Jun 23 09:44:03 diligent1 kernel: sddlmbj1: rw=1, want=6332971392,
limit=4183807887

 

 

running fsck.ext3 -n -f on this device yield the Below  output.

"

 Pass 1: Checking inodes, blocks, and sizes

Inode 192086020 has illegal block(s).  Clear? no

 

Illegal block #18620428 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620429 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620430 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620431 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620432 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620433 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620434 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620435 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620436 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620437 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620438 (774778414) in inode 192086020.  IGNORED.

Too many illegal blocks in inode 192086020.

Clear inode? no

 

Suppress messages? no

 

Illegal block #18620439 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620440 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620441 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620442 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620443 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620444 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620445 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620446 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620447 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620448 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620449 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620450 (774778414) in inode 192086020.  IGNORED.

Too many illegal blocks in inode 192086020.

Clear inode? no

 

Suppress messages? no

 

Illegal block #18620451 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620452 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620453 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620454 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620455 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620456 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620457 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620458 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620459 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620460 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620461 (774778414) in inode 192086020.  IGNORED.

Illegal block #18620462 (774778414) in inode 192086020.  IGNORED.

Too many illegal blocks in inode 192086020.

Clear inode? no

 

Suppress messages? no

 

 "

Do you think that running fsck with corrective actions will destroy part
of my data consistency? if the answer is yes is there any other way to
recover?

 

What do you think was the root cause for this issue ?

 

Please notice that this specific FS is more than 2TB size but configured
with msdos partition label.

 

 

Best regards

Yossi Yamin

Sr.Technical specialist 

Diligent Technologies, an IBM Company

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/ext3-users/attachments/20080625/b34a4743/attachment.htm>


More information about the Ext3-users mailing list