New read/write bug in FAT fs
One of the changesets posted by Linus on August 2 introduced a bug in the FAT fs:
Even when a fat32 fs is mounted read-write I now get error messages claiming the fs is 'read-only' when I try to write to it.
The only change I can see which fits the timing is to inode.c which was posted on August 2. Apologies if I am blaming the wrong changeset.
Could someone confirm this bug for me?
Thanks!
Quoted 6 lines · walt
One of the changesets posted by Linus on August 2 introduced a bug in the FAT fs:
Even when a fat32 fs is mounted read-write I now get error messages claiming the fs is 'read-only' when I try to write to it.
http://linus.bkbits.net:8080/linux-2.5/[email protected]?nav=index.html|ChangeSet@-4d
Signature · 2 lines
Tomasz Torcz "God, root, what's the difference?" [email protected] "God is more forgiving."
Quoted 3 lines · walt
Even when a fat32 fs is mounted read-write I now get error messages claiming the fs is 'read-only' when I try to write to it.
Okay, I've now found the comments about specifying values for iocharset and codepage, and read-write works again.
However, IMHO the 'mount' command should simply refuse to mount a FATfs read/write unless iocharset and codepage are specified. As things stand now, 'mount' reports the fs is mounted rw when it simply is not true.
Quoted 7 lines · walt
One of the changesets posted by Linus on August 2 introduced a bug in the FAT fs:
Even when a fat32 fs is mounted read-write I now get error messages claiming the fs is 'read-only' when I try to write to it.
Quoted 5 lines
The only change I can see which fits the timing is to
inode.cwhich was posted on August 2. Apologies if I am blaming the wrong changeset.Could someone confirm this bug for me?
This is intention.
The default codepage/iocharset which is easy to cause a mistake and unclear was deleted from fatfs. So default is mounted as read only.
You need to explicitly specify the "codepage" and "iocharset" options.
Signature · 1 line
OGAWA Hirofumi <[email protected]>
Quoted 6 lines · OGAWA Hirofumi
This is intention.
The default codepage/iocharset which is easy to cause a mistake and unclear was deleted from fatfs. So default is mounted as read only.
You need to explicitly specify the "codepage" and "iocharset" options.
To minimise confusion, is it an idea that NTFS and FAT use the same mount options? Right now NTFS uses "nls" and VFAT "iocharset".
Erik
Signature · 2 lines
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 -- | Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
Quoted 2 lines · Erik Mouw
To minimise confusion, is it an idea that NTFS and FAT use the same mount options? Right now NTFS uses "nls" and VFAT "iocharset".
"nls" option is used by only NTFS. Other filesystems is using "iocharset". Umm.. Why was "iocharset" option deprecated?
Signature · 1 line
OGAWA Hirofumi <[email protected]>