Bug#365608: usbmount can't mount FAT files system

Samson PIERRE

unread,

May 1, 2006, 9:30:15 AM5/1/06

to

Package: usbmount
Version: 0.0.10

Hello,
I have a USB device.
When the files system is ext3 or ext2(Formated "vfat" with mkfs.ext2 or
mkfs.ext3 under Debian), there is no problem for the automount.
But when the files system is vfat(Formated "FAT" under Windows XP, or
Formated "vfat" with mkfs.vfat under Debian), there is a lot of errors:

attempt to access beyond end of device
sda: rw=0, want=1985044, limit=503808
FAT: Directory bread(block 1985043) failed

attempt to access beyond end of device
[... ]

attempt to access beyond end of device
[...]

I have add vfat in the /etc/usbmount/usbmount.conf file:
FILESYSTEMS="ext2 ext3 vfat"

When I don't use usbmount, I do:
#mount -t vfat /dev/sda1 /mnt/storage/
And no problem to access data on the USB device.
So the problem is in the package usbmount.

Thx to try to resolve this bug.

Debian: 3.1r2
Kernel: 2.6.8-3-k7

usbmount_syslog.txt

Rogério Brito

unread,

Oct 19, 2008, 9:00:25 AM10/19/08

to

Hi, Samson.

On May 01 2006, Samson PIERRE wrote:
> I have a USB device.
> When the files system is ext3 or ext2(Formated "vfat" with mkfs.ext2 or
> mkfs.ext3 under Debian), there is no problem for the automount.

What exactly do you mean by "formatting 'vfat' with mkfs.ext{2,3}"? They
will only create ext2/3 fs, AFAIK.

> But when the files system is vfat(Formated "FAT" under Windows XP, or
> Formated "vfat" with mkfs.vfat under Debian), there is a lot of errors:
>
> attempt to access beyond end of device
> sda: rw=0, want=1985044, limit=503808
> FAT: Directory bread(block 1985043) failed

This is an error in the kernel. I guess that the kernel you were using
had/has a bug. Can you reproduce the problem with a newer kernel and a
recent usbmount?

BTW, it would help if you posted the output from "fdisk -l" on the
device that contains such partitions, to see exactly the limits of the
partition.

Thanks for using usbmount.

Regards, Rogério Brito.

--
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org

--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

YuGiOhJCJ

unread,

Oct 19, 2008, 11:40:11 AM10/19/08

to

Rogério Brito a écrit :

> Hi, Samson.
>
> On May 01 2006, Samson PIERRE wrote:
>
>> I have a USB device.
>> When the files system is ext3 or ext2(Formated "vfat" with mkfs.ext2 or
>> mkfs.ext3 under Debian), there is no problem for the automount.
>>
>
> What exactly do you mean by "formatting 'vfat' with mkfs.ext{2,3}"? They
> will only create ext2/3 fs, AFAIK.
>
>
>> But when the files system is vfat(Formated "FAT" under Windows XP, or
>> Formated "vfat" with mkfs.vfat under Debian), there is a lot of errors:
>>
>> attempt to access beyond end of device
>> sda: rw=0, want=1985044, limit=503808
>> FAT: Directory bread(block 1985043) failed
>>
>
> This is an error in the kernel. I guess that the kernel you were using
> had/has a bug. Can you reproduce the problem with a newer kernel and a
> recent usbmount?
>
> BTW, it would help if you posted the output from "fdisk -l" on the
> device that contains such partitions, to see exactly the limits of the
> partition.
>
> Thanks for using usbmount.
>
>
> Regards, Rogério Brito.
>
>

Sorry but I posted this bug 2 years ago.
I don't remember.
I am on Slackware Operating System now.
I think you can close this bug because I have no problem anymore with my
USB device.
Bye ;-)