thr3ads.net - Ext3 users - "Attempt to access beyond end of device" problem [Jun 2008]

If this information is useful, please help other people find it:
Share via:

Yamin, Yossi

2008-Jun-24 16:45 UTC

"Attempt to access beyond end of device" problem

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 attached output.

 

 

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/20080624/a07341d7/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fsck_sddlmbj1.zip
Type: application/x-zip-compressed
Size: 463793 bytes
Desc: fsck_sddlmbj1.zip
URL:
<http://listman.redhat.com/archives/ext3-users/attachments/20080624/a07341d7/attachment.bin>

Yamin, Yossi

2008-Jun-25 12:55 UTC

head link

"Attempt to access beyond end of device" problem

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>

Yamin, Yossi

2008-Jun-28 20:50 UTC

head link

debugfs question

Hi, 

I am trying to read a file directly from the disk using debugfs utility.

I am running "stat" on the file I want, filter out IND and Bind
blocks,
and then copy the data blocks using dd directly from the Disk.

On small files it work'd (13MB).

On big files (3.5 , 440 GB)  the size is the same but md5sum get differ.

What am I doing wrong?

I umount the FS before I start so the file is not changing.

 

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/20080628/1e51f6c5/attachment.htm>

Andreas Dilger

2008-Jul-02 07:28 UTC

head link

debugfs question

On Jun 28, 2008  23:50 +0300, Yamin, Yossi wrote:> I am trying to read a file directly from the disk using debugfs utility.
> 
> I am running "stat" on the file I want, filter out IND and Bind
blocks,
> and then copy the data blocks using dd directly from the Disk.
> 
> On small files it work'd (13MB).
> 
> On big files (3.5 , 440 GB)  the size is the same but md5sum get differ.
> 
> What am I doing wrong?
What you are doing wrong is that you aren't using the debugfs
"dump"
command, which will do what you are trying to do.


Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.

Ext3 users - Jun 2008 - "Attempt to access beyond end of device" problem

"Attempt to access beyond end of device" problem

"Attempt to access beyond end of device" problem

debugfs question

debugfs question