* [2.6.8-rc2-bk] New read/write bug in FAT fs
@ 2004-08-04 11:57 walt
2004-08-04 12:23 ` walt
` (2 more replies)
0 siblings, 3 replies; 6+ messages in thread
From: walt @ 2004-08-04 11:57 UTC (permalink / raw)
To: Linux Kernel, hirofumi
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!
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [2.6.8-rc2-bk] New read/write bug in FAT fs
2004-08-04 11:57 [2.6.8-rc2-bk] New read/write bug in FAT fs walt
@ 2004-08-04 12:23 ` walt
2004-08-04 13:19 ` Tomasz Torcz
2004-08-04 13:31 ` OGAWA Hirofumi
2 siblings, 0 replies; 6+ messages in thread
From: walt @ 2004-08-04 12:23 UTC (permalink / raw)
Cc: Linux Kernel, hirofumi
walt wrote:
> 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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [2.6.8-rc2-bk] New read/write bug in FAT fs
2004-08-04 11:57 [2.6.8-rc2-bk] New read/write bug in FAT fs walt
2004-08-04 12:23 ` walt
@ 2004-08-04 13:19 ` Tomasz Torcz
2004-08-04 13:31 ` OGAWA Hirofumi
2 siblings, 0 replies; 6+ messages in thread
From: Tomasz Torcz @ 2004-08-04 13:19 UTC (permalink / raw)
To: Linux Kernel
On Wed, Aug 04, 2004 at 04:57:29AM -0700, walt wrote:
> 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/cset@1.1878?nav=index.html|ChangeSet@-4d
--
Tomasz Torcz "God, root, what's the difference?"
zdzichu@irc.-nie.spam-.pl "God is more forgiving."
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [2.6.8-rc2-bk] New read/write bug in FAT fs
2004-08-04 11:57 [2.6.8-rc2-bk] New read/write bug in FAT fs walt
2004-08-04 12:23 ` walt
2004-08-04 13:19 ` Tomasz Torcz
@ 2004-08-04 13:31 ` OGAWA Hirofumi
2004-08-04 13:45 ` Erik Mouw
2 siblings, 1 reply; 6+ messages in thread
From: OGAWA Hirofumi @ 2004-08-04 13:31 UTC (permalink / raw)
To: walt; +Cc: Linux Kernel
walt <wa1ter@myrealbox.com> writes:
> 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?
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.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [2.6.8-rc2-bk] New read/write bug in FAT fs
2004-08-04 13:31 ` OGAWA Hirofumi
@ 2004-08-04 13:45 ` Erik Mouw
2004-08-04 14:17 ` OGAWA Hirofumi
0 siblings, 1 reply; 6+ messages in thread
From: Erik Mouw @ 2004-08-04 13:45 UTC (permalink / raw)
To: OGAWA Hirofumi; +Cc: walt, Linux Kernel
On Wed, Aug 04, 2004 at 10:31:18PM +0900, OGAWA Hirofumi wrote:
> 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
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [2.6.8-rc2-bk] New read/write bug in FAT fs
2004-08-04 13:45 ` Erik Mouw
@ 2004-08-04 14:17 ` OGAWA Hirofumi
0 siblings, 0 replies; 6+ messages in thread
From: OGAWA Hirofumi @ 2004-08-04 14:17 UTC (permalink / raw)
To: Erik Mouw, aia21; +Cc: walt, Linux Kernel
Erik Mouw <erik@harddisk-recovery.com> writes:
> 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?
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2004-08-04 14:18 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-08-04 11:57 [2.6.8-rc2-bk] New read/write bug in FAT fs walt
2004-08-04 12:23 ` walt
2004-08-04 13:19 ` Tomasz Torcz
2004-08-04 13:31 ` OGAWA Hirofumi
2004-08-04 13:45 ` Erik Mouw
2004-08-04 14:17 ` OGAWA Hirofumi
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.