You are not logged in.
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/cdrom /media/cdrom auto ro,user,noauto,unhide 0 0
/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
UUID=126b1ae8-34c3-4f68-8d36-fecaf3eecc45 swap swap defaults 0 0
UUID=29c68b67-6585-4739-b2db-41df3f3e8ad1 / ext3 defaults 0 1
UUID=3087169d-5aca-4233-be45-b7426c9a41a1 /boot ext2 defaults 0 1
UUID=f6fec2fa-fde5-4a6e-b30c-9662a78b6654 /home ext3 defaults 0 1
//192.168.1.121/"Storage Volume" /mnt/shares/arch cifs users,noatime,username=ted,password=computer,workgroup=WORKGROUP 0 0
Looks fine to me.
Last edited by mooreted (2009-01-16 20:18:14)
Offline
That's the network share, right? Why does it have quotes, and not an escaped space?
Offline
Assuming line 15 is your samba share, it could be choking on the quotes, try changing
//192.168.1.121/"Storage Volume"
to
//192.168.1.121/Storage\ Volume
# or
"//192.168.1.121/Storage Volume"
Offline
Nope, it doesn't like that either.
It mounts fine from the command-line.
mount -t cifs //192.168.1.121/"Storage Volume" /mnt/shares/arch -o username=ted,password=computer
Last edited by mooreted (2009-01-14 19:50:43)
Offline
An ugly 'hack' is to put it in rc.local, I do this with a USB-drive (there might be smarter alternatives), because the kernel doesn't find the drive before /etc/fstab is read I've put a drive in /etc/fstab. This might solve your problem, but it's "ugly".
We met up with the aliens and guess what? They have no word for fluffy!
Offline
I don't care about elegant vs ugly, I only care about works vs doesn't work,
I'll give that a shot, thanks.
Offline
which text editor did you use to edit the file ?
I had a similar bug with another of my config files some time ago, it was because when using vi, if you type ctrl-d (the command to scroll down half a screen) while in insertion mode and at the end of a line, it inserts an hidden character, which makes the line invalid (when I did shift-j on that line, a blank character appeared at the end)
try to delete and rewrite the line (manually, not by cutting and pasting)
well, that makes me think I should post a bug report to vi developpers
NB : very not sure it is the cause of your bug, but just try, it will not hurt
take time to daydream, inspiration comes ...
Offline
which text editor did you use to edit the file ?
I had a similar bug with another of my config files some time ago, it was because when using vi, if you type ctrl-d (the command to scroll down half a screen) while in insertion mode and at the end of a line, it inserts an hidden character, which makes the line invalid (when I did shift-j on that line, a blank character appeared at the end)
try to delete and rewrite the line (manually, not by cutting and pasting)well, that makes me think I should post a bug report to vi developpers
NB : very not sure it is the cause of your bug, but just try, it will not hurt
Huh, hadn't thought of that. I used Nano. Never run into that problem before. I'll try it.
Thanks.
Offline
Try changing the share name to something else, such as just storage, that may work.
Failing that I have had problems with config files before when they haven't had an end of line character at the end of them, which may or may not be the case here, but you could try just adding a blank line at the end of the file. Not sure why that happens now and again, but it's something I have come across before.
Offline
Try changing the share name to something else, such as just storage, that may work.
Failing that I have had problems with config files before when they haven't had an end of line character at the end of them, which may or may not be the case here, but you could try just adding a blank line at the end of the file. Not sure why that happens now and again, but it's something I have come across before.
I would love to take the spaces out of all the file names on the server, unfortunately it's not my server.
I'll try the EOF idea, you never know.
Thanks.
Offline
I had completely forgotton. There is a special escape character for fstab entries. "\040".
So, the fstab looks like this:
//192.168.1.121/Storage\040Volume /mnt/shares/arch cifs users,noatime,username=ted,password=computer,workgroup=WORKGROUP 0 0
Note the Storage\040Volume part of the entry.
Offline
Storage\040Volume
"\040" is simply a space character, so Storage\ Volume should work as well, except if mount splits the fstab lines in fields even on escaped spaces. Is it a bug ?
take time to daydream, inspiration comes ...
Offline
It is strange, but when I searched for spaces in fstab, every article I found said you had to use the ascii number with a slash "/040". Linux never has liked spaces in file names much.
Offline