Linux Archive - "Attempt to access beyond end of device" problem

Linux Archive (http://www.linux-archive.org/)

- EXT3 Users (http://www.linux-archive.org/ext3-users/)

- - "Attempt to access beyond end of device" problem (http://www.linux-archive.org/ext3-users/113275-attempt-access-beyond-end-device-problem.html)

"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

*

*

*

_______________________________________________
Ext3-users mailing list
Ext3-users@redhat.com
https://www.redhat.com/mailman/listinfo/ext3-users

"Attempt to access beyond end of device" problem

Yamin, Yossi wrote:
> 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

...

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

Hm, I think you just stated the root cause. Did the filesystem work
fine until you rebooted it? Did it used to be 8T? And did you use
parted to create it?

Parted wrongly allows you to make a >2T msdos partition table and pokes
it directly into the kernel, but the on-disk format cannot hold the
large value. So when you reboot, it's read as something smaller.

You might be able to do a trick where you create a new GPT label in
place of the old DOS label, with the same start point as the dos label,
but with a correct endpoint.

I would not repair the fs; if my guess is right, 3/4 of it is now
unreachable and fsck will probably do heavy damage.

-Eric

_______________________________________________
Ext3-users mailing list
Ext3-users@redhat.com
https://www.redhat.com/mailman/listinfo/ext3-users

"Attempt to access beyond end of device" problem

HI,
Thanks for the quick response.
I think the situation is different then what you describe since we have
abut 10 FS with the same size 2142.1 GB that have no problem.
Thanks,
Yossi

-----Original Message-----
From: Eric Sandeen [mailto:sandeen@redhat.com]
Sent: Wednesday, June 25, 2008 4:56 PM
To: Yamin, Yossi
Cc: ext3-users@redhat.com
Subject: Re: "Attempt to access beyond end of device" problem

Yamin, Yossi wrote:
> 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

...

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

Hm, I think you just stated the root cause. Did the filesystem work
fine until you rebooted it? Did it used to be 8T? And did you use
parted to create it?

Parted wrongly allows you to make a >2T msdos partition table and pokes
it directly into the kernel, but the on-disk format cannot hold the
large value. So when you reboot, it's read as something smaller.

You might be able to do a trick where you create a new GPT label in
place of the old DOS label, with the same start point as the dos label,
but with a correct endpoint.

I would not repair the fs; if my guess is right, 3/4 of it is now
unreachable and fsck will probably do heavy damage.

-Eric

_______________________________________________
Ext3-users mailing list
Ext3-users@redhat.com
https://www.redhat.com/mailman/listinfo/ext3-users

"Attempt to access beyond end of device" problem

Yamin, Yossi wrote:
> HI,
> Thanks for the quick response.
> I think the situation is different then what you describe since we have
> abut 10 FS with the same size 2142.1 GB that have no problem.

Hm, ok, you said that it was > 2T... I guess that's TiB vs. TB.

Then perhaps it is just localized corruption (hard to say from *what*)
and an e2fsck might fix it up just fine.

-Eric

_______________________________________________
Ext3-users mailing list
Ext3-users@redhat.com
https://www.redhat.com/mailman/listinfo/ext3-users