lkml.org 
[lkml]   [2001]   [Jul]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
Subjectvfat: attempt to access beyond end of device
Hello,

I wrote this mail to chaffee@bmrc.cs.berkeley.edu as suggested
in Documentation/filesystems/vfat.txt, but it seems, this
address is not valid (550 <chaffee@bmrc.cs.berkeley.edu>...
Host unknown), so I try here :)

I have a 76Gig FAT32 Partition and mount it under Linux using
the vfat filesystem.

The filesystem is filled up to 85% at the moment and I
experience problems in writing new files on it under Linux.

Filesystem Size Used Avail Use% Mounted on
/dev/hdc1 76G 65G 12G 85% /data

When I try to write new files on it, I get:
kernel: attempt to access beyond end of device
kernel: 16:01: rw=0, want=2081231810, limit=80035798
kernel: dev = 16:01, ino = -2120058812
kernel: Filesystem panic (dev 16:01).
kernel: msdos_write_inode: unable to read i-node block
kernel: File system has been set read-only
kernel: attempt to access beyond end of device
kernel: 16:01: rw=0, want=2081231810, limit=80035798
kernel: dev = 16:01, ino = -2120058812
kernel: Filesystem panic (dev 16:01).
kernel: msdos_write_inode: unable to read i-node block

or (with 2.2.19):
kernel: attempt to access beyond end of device
kernel: 16:01: rw=0, want=2080939906, limit=80035798
kernel: dev 16:01 blksize=512 blocknr=-133087484 sector=-133087484 size=512 count=1
kernel: dev = 16:01, ino = -2129399739
kernel: Filesystem panic (dev 16:01).
kernel: msdos_write_inode: unable to read i-node block
kernel: File system has been set read-only
kernel: attempt to access beyond end of device
kernel: 16:01: rw=0, want=2080939906, limit=80035798
kernel: dev 16:01 blksize=512 blocknr=-133087484 sector=-133087484 size=512 count=1
kernel: dev = 16:01, ino = -2129399739
kernel: Filesystem panic (dev 16:01).
kernel: msdos_write_inode: unable to read i-node block

Copying the same files under Windows works fine and I'm able
to access them under Linux after copying them under Windows.

I found, that this ever happen, if the Filesystem is filled
up to 12G free space - last time i removed some other files
and defragmented the filesystem and then everything worked
fine up to this magic 65G border. Now it happens again.

Windows scandisk and Linux dosfsck don't report any errors
on the filesystem (of course, after the error they do, but
not before), but the write error is reproduceable for me.

I tried to copy a large file from the disk to itself - first
under Windows, next under Linux and this both worked fine, but
copying other files to other directories doesn't work
either.

It seems, when I copy some files under Windows, I'm able to
copy some more files under Linux too (something around 50
or 100 Megs) and then the problem occures again.

I'm using a 2.4.6 kernel at the moment, but the same problem
occured with 2.4.5 and 2.2.19 kernel too.

I guess, it's something like a bit overflow in some variable
while creating new meta structures or something, dunno what
vfat has there :)

Can you help me / can I help you to trace this down?


Thanks for your work.


regards,
Mario
--
Mario 'BitKoenig' Holbe <Mario.Holbe@RZ.TU-Ilmenau.DE>

So long and thanks for all the books.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:17    [W:0.045 / U:1.912 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site