Cannot create regular file, read only file system? I could do it yesterday ...

[IronFox]

All my torrents go to my home/username/Download/ folder, I could read/write yesterday but now I cant even copy the files to a flash drive. The error i get is "Cannot create regular file '/home/username/Download/file' : Read only file system.

Using F11

[Hlingler]

"All my torrents..." Your HDD/partition is perhaps full ???


V

P.S. Please post Fedora Release number and architecture when asking questions.

[IronFox]

I think I may have figured it out. I just installed samba and rebooted and that fixed the problem, i guess. After the reboot I was able to read/write.

[kramulous]

Guys,

I keep getting this error as well. A reboot fixes the problem but getting sick of it.

After something is mounted (beit a samba share or a usb), my entire disk becomes read only

Dialogue box:
Error while creating directory untitled folder.
There was an error creating the directory in /home/username/Destop.
\/ Show more details
Error creating the directory: Read-only file system

Is this happening to anybody else?

[kramulous]

Linux my.hostname.not.real 2.6.29.5-191.fc11.x86_64 #1 SMP Tue Jun 16 23:23:21 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux

[JEO]

Did you mean /home/user/Desktop in the error message?

Are you sure the entire filesystem is becoming read-only because I would expect that to crash horribly or hard lock the system?

How long after you mount something does the error occur?

[kramulous]

Almost instantly (measured in seconds). A lot of things would stop working.

I rebooted and stuck my usb in again and the same problem ... all of /home was read only (/home is a separate partition ext3, I didn't test if I could write else where). Most frustrating. It happened for many days in a row after clients needed me to check things out. Not all samba shares would trigger the problem though (The trigger of the last samba share was on a windows system ... the linux smb shares were fine).

Now, when I installed F11 I did so without the clean install method ... the upgrade mechanism which I know is not recommended. Because of an issue I was having with File browsers only opening on one X Server, I, stupidly, added the testing repo and did a full update. Although my file browser issue was fixed, this is when the read-only issue began. Soon after, I disabled the testing repo ... possible the second nail in the coffin.

Because of this and some issues I was having with gcc 4.4.0, I have just reverted to F10 (until F12 arrives). I hung around the forums for a bit in case anybody wanted me to do some diagnosis, but I had work to do .... I still really appreciate it though.

[Min]

I have this problem too (cannot write to fat32 file system), even though it's fine in the past. Detail

F11, X86_64

#
# /etc/fstab
# Created by anaconda on Wed Jun 10 09:50:20 2009
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or vol_id(8) for more info
#
UUID=8ba4184c-65fa-45e5-951b-3374d680ee9f /boot ext3 defaults 1 2
/dev/mapper/vg_himitsu-lv_root / ext4 defaults 1 1
/dev/mapper/vg_himitsu-lv_swap swap swap defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts defaults 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
/dev/sda2 /media/Macintosh\040HD hfsplus rw 0 0
/dev/sda4 /media/WINDOWS\040HD msdos rw 0 0

etc/mtab

/dev/mapper/vg_himitsu-lv_root / ext4 rw 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
devpts /dev/pts devpts rw 0 0
tmpfs /dev/shm tmpfs rw 0 0
sunrpc /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0
/dev/sda2 /media/Macintosh\040HD hfsplus rw 0 0
/dev/sda4 /media/WINDOWS\040HD msdos rw 0 0

[JEO]

It shows it's mounted read/write. Permissions problem? If you can write to it as root, I would say so.

[Min]

when I right klik the munted device and select permissions tab, it says
permission for "xxxxxx" cannot be determined.

And i cannot even copy file to that partition even as root !!!

[JEO]

That's odd.

Try changing the line in /etc/fstab

/dev/sda4 /media/WINDOWS\040HD msdos rw 0 0

to

/dev/sda4 /media/WINDOWS\040HD vfat defaults 0 0

[JEO]

Also can you explain what the backslash in the name WINDOWS\040HD is for?

[Min]

its for space (WINDOWS HD) but IIRC shouldn't space 20? Anyway it was work before so it shouldn't be a problem with that space

[JEO]

Yes 020 hexadecimal or 032 decimal. You should try fixing that also, because some utilities may not like that 040 character.

[Min]

so what should i change it to?
/dev/sda4 /media/WINDOWS\020HD msdos rw 0 0
or
/dev/sda4 /media/WINDOWS\%20HD msdos rw 0 0