https://bugzilla.novell.com/show_bug.cgi?id=331255 User brian@clusterfs.com added comment https://bugzilla.novell.com/show_bug.cgi?id=331255#c4 Brian Murrell <brian@clusterfs.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME | --- Comment #4 from Brian Murrell <brian@clusterfs.com> 2008-02-14 11:08:40 MST --- (In reply to comment #3 from Ruediger Oertel)
other network filesystems are normally mounted by their respective rc-scripts, e.g. nfs,smbfs,autofs,open-iscsi,...
Has NFS really gotten that complicated that it needs its own rc script? For a long time, NFS has been able to use _netdev in /etc/fstab to simply delay mounting until the network was available.
Since the requirements of these filesystems vary from type to type it would not make too much sense to have a generic version to "catch all" network filesystem mounting.
Do you maintain that position even for network filesystems whose only requirement is that the network be available? It seems silly to have an initscript that simply does: mount -t <fstype> -a That is simply placed after or dependent on the network start initscript.
SLES9 for example had a package lustre-lite with the rcscript /etc/init.d/lustrefs taking care of mounting this type of filesystem.
Heh. You must have chosen the lustre-lite/lustrefs example for a reason. :-) Indeed, in the SLES9 days, yes, Lustre had it's own tools to bring up the filesystem. We went to great pains to eliminate that initscript and work with standard tools such as mount, mkfs, and tunefs. Now Lustre, on all servers and clients can be mounted with nothing more complicated than an /etc/fstab entry, IFF that entry can be dependent on the network being up, which historically is what the _netdev fstab option was for. I'm getting a feeling though, that no matter what I say you won't rethink your abolishment of _netdev or any other facility that allows /etc/fstab entries to delay mounting until after the network is up. Is that true? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.