Re: Filesystem checks with noauto
The last two numbers in the line are the order in which to run fsck and backups. So if you replace "1 2" with "0 0", it will do what you want. Benny Dima Veselov schrieb am Di., 27. Okt. 2020, 18:37: > Greetings, > > I have a Gluster volume on NetBSD box. It has long > description in fstab > > /usr/pkg/sbin/mount_glusterfs#gfs01:/gva /gvapuffs > noauto,direct-io-mode=false,rw,backup-volfile-servers=gfs02:gfs03:gfs04:gfs05:gfs06 > > 1 2 > > I assume noauto should disable filesystem checks, but the > server can not boot. The first actual problem is checking > filesystem that may not be available, and second that it > tries to mount glusterfs before /usr is available and > /usr/pkg/sbin/mount_glusterfs exists. > > What may I do to workaround this? For now I have to mount > it manually. And will it be fixed in future release? > > -- > Sincerely yours, > Dima Veselov > Physics R Establishment of Saint-Petersburg University >
Re: Filesystem checks with noauto
Hi, > > I have a Gluster volume on NetBSD box. It has long > > description in fstab > > > > /usr/pkg/sbin/mount_glusterfs#gfs01:/gva /gvapuffs > > noauto,direct-io-mode=false,rw,backup-volfile-servers=gfs02:gfs03:gfs04:gfs05:gfs06 > > > > 1 2 > > I assume noauto should disable filesystem checks, > Well noauto simply means don't automatically mount during boot. >From fstab(5): The sixth field, (fs_passno), is used by the fsck(8) program to determine the order in which file system checks are done at reboot time. If the sixth field is not present or zero, a value of zero is returned and fsck(8) will assume that the file system does not need to be checked. So, I suggest changing the "2" to "0" above, or just deleting it. Regards, Julian
Re: Filesystem checks with noauto
On Tue, 27 Oct 2020 20:36:59 +0300 Dima Veselov wrote: > Greetings, > > I have a Gluster volume on NetBSD box. It has long > description in fstab > > /usr/pkg/sbin/mount_glusterfs#gfs01:/gva /gvapuffs > noauto,direct-io-mode=false,rw,backup-volfile-servers=gfs02:gfs03:gfs04:gfs05:gfs06 > > 1 2 > > I assume noauto should disable filesystem checks, but the > server can not boot. The first actual problem is checking > filesystem that may not be available, and second that it > tries to mount glusterfs before /usr is available and > /usr/pkg/sbin/mount_glusterfs exists. > > What may I do to workaround this? For now I have to mount > it manually. And will it be fixed in future release? > > -- > Sincerely yours, > Dima Veselov > Physics R Establishment of Saint-Petersburg University Well noauto simply means don't automatically mount during boot. As for the second issue, have you tried critical_filesystems_local="/usr" in /etc/rc.conf? Not sure how fstab determines mount priority, would it be random or simply same order as written on each line?
Filesystem checks with noauto
Greetings, I have a Gluster volume on NetBSD box. It has long description in fstab /usr/pkg/sbin/mount_glusterfs#gfs01:/gva /gvapuffs noauto,direct-io-mode=false,rw,backup-volfile-servers=gfs02:gfs03:gfs04:gfs05:gfs06 1 2 I assume noauto should disable filesystem checks, but the server can not boot. The first actual problem is checking filesystem that may not be available, and second that it tries to mount glusterfs before /usr is available and /usr/pkg/sbin/mount_glusterfs exists. What may I do to workaround this? For now I have to mount it manually. And will it be fixed in future release? -- Sincerely yours, Dima Veselov Physics R Establishment of Saint-Petersburg University
