From: Piotr R. K. <pio...@mo...> - 2015-10-22 10:19:14
|
Hello, what Linux distribution are you using? Do you have package “fuse-utils” installed? The lack of this package installed probably causes this problem. The entry should now look like this: mfsmount /mnt/mfs fuse defaults 0 0 There’s no need to set mfsmaster=mfsmaster and mfsport=9421 since they are default values. If in your environment they are different than defaults, you should include them, e.g.: mfsmount /mnt/mfs fuse defaults,mfsmaster=mymaster.xyz.lan,mfsport=9921 0 0 As far as I remember there’s no need to use _netdev now. Best regards, -- Piotr Robert Konopelko MooseFS Technical Support Engineer | moosefs.com <https://moosefs.com/> > On 22 Oct 2015, at 4:56 am, 18...@gm... wrote: > > I'm using MooseFS 2.0.77 but I can't put mfsmount on /etc/fstab > > # cat /etc/fstab | grep mfsmount > mfsmount /mnt/mfs fuse mfsmaster=mfsmaster,mfsport=9421,_netdev 0 0 > > # mount /mnt/mfs > mount: wrong fs type, bad option, bad superblock on mfsmount, > missing codepage or helper program, or other error > (for several filesystems (e.g. nfs, cifs) you might > need a /sbin/mount.<type> helper program) > In some cases useful info is found in syslog - try > dmesg | tail or so > > Then I have to manually run mfsmount. > > What can I do to fix this? > Thanks, > ------------------------------------------------------------------------------ > _________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users |