View Full Version : Cannot create regular file, read only file system? I could do it yesterday ...

16th June 2009, 03:38 AM
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

16th June 2009, 03:39 AM
"All my torrents..." Your HDD/partition is perhaps full ???


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

16th June 2009, 04:08 AM
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.

27th July 2009, 11:15 PM

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?

27th July 2009, 11:18 PM
Linux my.hostname.not.real #1 SMP Tue Jun 16 23:23:21 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux

28th July 2009, 01:15 AM
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?

28th July 2009, 03:02 AM
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.

4th August 2009, 11:47 PM
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


/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

4th August 2009, 11:58 PM
It shows it's mounted read/write. Permissions problem? If you can write to it as root, I would say so.

5th August 2009, 12:33 AM
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 !!!

5th August 2009, 01:07 AM
That's odd.

Try changing the line in /etc/fstab

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


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

5th August 2009, 01:10 AM
Also can you explain what the backslash in the name WINDOWS\040HD is for?

5th August 2009, 01:27 AM
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

5th August 2009, 01:35 AM
Yes 020 hexadecimal or 032 decimal. You should try fixing that also, because some utilities may not like that 040 character.

5th August 2009, 01:40 AM
so what should i change it to?
/dev/sda4 /media/WINDOWS\020HD msdos rw 0 0
/dev/sda4 /media/WINDOWS\%20HD msdos rw 0 0

5th August 2009, 01:45 AM
Leave it as is, 040 is octal code for space.

5th August 2009, 02:01 AM
changing it to vfat didn't solved the problem (in fact i think i was mess it when remounted the drive, it should be vfat yesterday). Any other idea?

5th August 2009, 02:14 AM
I find something strange here. If it say read only file system, how did songbird can save a lyric to metadata (my music collection is in that windows partition). And when i select metadata editor it say it can not be changed =(

5th August 2009, 02:14 AM
I'm assuming you also changed the rw to defaults and the line now reads:

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

Let's try a few tests then. Open a terminal window and post the output of the followng commands:

su -

(if /dev/sd4 is not listed then type mount /dev/sda4"

cd "/media/WINDOWS HD"
ls -l
touch testfile.txt

5th August 2009, 02:18 AM
Another assumption I made is that you either rebooted or did the following after changing the /etc/fstab line:

su -
umount /dev/sda4
mount /dev/sda4

5th August 2009, 02:41 AM
mine is
/dev/sda4 /media/WINDOWS\040HD vfat rw 0 0

5th August 2009, 03:07 AM
Okay, so change it to the line I put in post 19, then remount it as in post 20, then do the tests in post 19.

5th August 2009, 03:28 AM
Wait, it most likely that the partition it self is might be corrupt!!!! Is there any disk checking software you recommended?

5th August 2009, 03:32 AM
If you can read your data then back it up somewhere else first. Filesystem check can sometimes make things worse. The volume has to be unmounted first. Make sure the umount command succeeds. To check filesystem using Fedora, open terminal

su -
umount /dev/sda4
fsck.vfat /dev/sda4

5th August 2009, 10:24 AM
I finally can copy the file after checking the disk with xp and there really was a problem with the partition

6th August 2009, 08:59 AM
Two days after this episode my drive failed (not saying one caused the other). It was a 2.5" 10K Raptor (or something - not sitting at my work machine). The computer was 3 months old.