I can mount it as read only (even for root!








cp: cannot create regular file `./external/logclock': Read-only file system




cp: cannot create regular file `./external/logclock': Read-only file system
josiah-HP-Compaq josiah # cat /etc/mtab
/dev/sda1 / reiserfs rw,notail,user_xattr 0 0
proc /proc proc rw,noexec,nosuid,nodev 0 0
none /sys sysfs rw,noexec,nosuid,nodev 0 0
fusectl /sys/fs/fuse/connections fusectl rw 0 0
none /sys/kernel/debug debugfs rw 0 0
none /sys/kernel/security securityfs rw 0 0
none /dev devtmpfs rw,mode=0755 0 0
none /dev/pts devpts rw,noexec,nosuid,gid=5,mode=0620 0 0
none /dev/shm tmpfs rw,nosuid,nodev 0 0
none /var/run tmpfs rw,nosuid,mode=0755 0 0
none /var/lock tmpfs rw,noexec,nosuid,nodev 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,noexec,nosuid,nodev 0 0
gvfs-fuse-daemon /home/josiah/.gvfs fuse.gvfs-fuse-daemon rw,nosuid,nodev,user=josiah 0 0
/dev/sdb1 /home/josiah/external vfat rw 0 0




josiah@josiah-HP-Compaq ~ $ cp ./logclock ./external/
cp: cannot create regular file `./external/logclock': Read-only file system
josiah@josiah-HP-Compaq ~ $ cat /etc/mtab
/dev/sda1 / reiserfs rw,notail,user_xattr 0 0
proc /proc proc rw,noexec,nosuid,nodev 0 0
none /sys sysfs rw,noexec,nosuid,nodev 0 0
fusectl /sys/fs/fuse/connections fusectl rw 0 0
none /sys/kernel/debug debugfs rw 0 0
none /sys/kernel/security securityfs rw 0 0
none /dev devtmpfs rw,mode=0755 0 0
none /dev/pts devpts rw,noexec,nosuid,gid=5,mode=0620 0 0
none /dev/shm tmpfs rw,nosuid,nodev 0 0
none /var/run tmpfs rw,nosuid,mode=0755 0 0
none /var/lock tmpfs rw,noexec,nosuid,nodev 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,noexec,nosuid,nodev 0 0
gvfs-fuse-daemon /home/josiah/.gvfs fuse.gvfs-fuse-daemon rw,nosuid,nodev,user=josiah 0 0
/dev/sdb1 /home/josiah/external vfat rw 0 0
josiah@josiah-HP-Compaq ~ $ sudo cp ./logclock ./external/
[sudo] password for josiah:
cp: cannot create regular file `./external/logclock': Read-only file system




sudo umountsudo mount /dev/sdb1 /home/josiah/external
September 10th, 2010, 05:14 PM
ok, I solved my problem. I hadn't found anything that worked with linux, but I ran the chkdsk utility via the windows command line to fix it and it succeeded (though it took *forever*). I don't like to admit that I was able to do something in windows that I couldn't on linux, but it's sort of because windows ****ed up it's own file system in the first place, so whatever.











Users browsing this forum: Google Adsense [Bot], iowabeakster, proxima_centauri, rkmugen and 31 guests