Question about fstab

sudo mount /dev/disk/by-id/ata-Maxtor_6Y080L0_Y2F0E7RE-part9 /dati
it’s ok.

But if i modify my /etc/fstab:
/dev/disk/by-id/ata-Maxtor_6Y080L0_Y2F0E7RE-part9 /dati ext3 acl,user_xattr 0 0
and i logout from the session and rather then i reaccess the folder dati don’t contain any data.

/dati
Group: users
Owner: myself

changes in /etc/fstab will have effect after reboot

i’d never seen that user_xattr before so wonder if you have configured
your POSIX Access Control Lists

and, also i wonder if you modified fstab (and saved it with root
powers) and then rebooted (i may be wrong, but i think just logging
out from that session, and then back in will cause the partition to be
mounted–so if is not mounted, then it must empty, right?)


palladium

Do this via Yast - System - Partitioner. It will avoid spaces, wrong attributes etc.

I have hope was sufficient simply close the session.

However now go good.

Knurpht
When possible i prefer avoid graphical systems to resolve problem.

I forgot to set mount points for an ntfs and fat32 partition on a 11.2 install. In the past I have successfully edited fstab and added partition mount points. However, on 11.2 this didn’t work. I even tried the older /dev/sda5 type syntax as an alternative.

First I cleaned up fstab by removing all my edits (back to original condition) and verified my off system backups were good. Then I used the YaST->System->Partitioner (a graphical interface), selected the partition and used “Edit” only to add the mount point. I crossed my fingers, took a big gulp and ran the partitioner. It correctly installed the mount points. Afterwards I rebooted to check it and everything was good.

The ntfs is an installed XP multi-boot and it still boots. Still running partitioner software on an otherwise functional partition takes real faith. If you mess up, you have backups and a reinstall.

Wrong.
They’ll have effect next time you mount a file system.

That’s probably just because there’s nothing mounted in it.
To find out which filesystems are currently mounted, just type : “sudo mount” (without argument) in a terminal.

Perfectly correct, actually. They may take effect when you reboot because the filesystem is remounted, but they still take effect when you reboot - and given the context, it was a perfectly decent answer.

If you want to be a pedant…

?!
When you reboot, they definitely take effect. But you don’t have to reboot for fstab changes to take effect, it’s enough to umount/remount a filesystem. There is nothing wrong with that, it’s just a fact. It might not be possible with any fs (like / or /var) nor in any situation, but for a filesystem, obviously containing data, which was supposed to be mounted in the folder /dati, you can edit fstab hundred times and remount /dati without rebooting. So the correct answer is: Don’t reboot because of that! Don’t even close your session! Take the right changes in fstab and remount your filesystem properly. That doesn’t mean that you should not reboot or restart your session. You can do that if you enjoy rebooting. It’s just not necessary. And you wouldn’t reboot either if you had to write mountpoints in fstab for too many filesystems.

If you make an edit to /etc/fstab and save the file it will read it and apply the changes. All you have to do is make the system mount the drives manually. This will require a reboot, or one can open a terminal window and type in the following.

sudo mount -a

This will mount all mountable drives. It can be put into a script and placed in Autostart, if one adds the command to SUDU in YaST. The mount command requires root access if it is run manually.

:stuck_out_tongue:

When you reboot, they definitely take effect.

So Rhaddamant was correct then?

All I’m saying is storming into a thread claiming “Wrong…” seems a little confrontational when the answer the first person gave was almost certainly perfectly sufficient.

I don’t think Rhaddamant was claiming that was the only way to do it. You could have simply said “It’s also possible by remounting the filesystem…”

Capice?

Changes in fstab take effect immediately, and it is wrong to pretend the contrary. So don’t! By doing that, you’re simply giving a false information.

Remounting a filesystem is all you need, as I explained, and so did Wilson_Phillips more concisely (and more clearly) in the post above.

But I’m quite sure you know that already. There’s no need to discuss about that and I won’t.

Do they! I stand corrected.

Remounting a filesystem is all you need, as I explained, and so did Wilson_Phillips more concisely (and more clearly) in the post above.

Oh - no. Hang on. They don’t take effect immediately. :slight_smile:

What Rhaddamant said was fine. If you want to add to it, add to it, but don’t run around claiming people are wrong when they’re not, then getting on your high horse when people call you up about it in a slightly jokey fashion.

No offence was meant. Carry on, have fun!.. :wink:

As I said, ANY change in fstab is read immediately by the system and is in full effect.:slight_smile:

You just won’t see or be able to use new drives till you mount them.:wink:

Chill out guys. It’s all good.

Not quite. Nothing is watching fstab. It’s just a plain text file like any other. Nothing magical happens when it is changed. In fact you could put rubbish into it, and nothing would happen until it gets used. But when you do use it, like running df, mount, etc. then it gets read.

You just won’t see or be able to use new drives till you mount them.

This is correct.

Hmmmm, If I make a change, I see it happen as soon as I save the file.

Sure, just like any other file on the system. Nothing odd about that. But nothing acts on the change until a program that uses fstab is run, e.g. df, mount, etc.

please try again wrote:
> They’ll have effect next time you mount a file system.

thanks…i probably knew that some years ago, but forgot…


palladium