Re: filesystem mount problem
On July 21, 2019 1:44:13 PM PDT, Ian Lepore wrote: >On Sun, 2019-07-21 at 15:07 -0400, AN wrote: >> Hi: >> >> FreeBSD FreeBSD_13 13.0-CURRENT FreeBSD 13.0-CURRENT #102 r350187: >> Sat Jul >> 20 19:04:30 EDT 2019 >> root@FreeBSD_13:/usr/obj/usr/src/amd64.amd64/sys/MYKERNEL amd64 >> 1300036 >> >> I would appreciate some help with the following problem. >> >> /etc/fstab: >> # Device Mountpoint FStype Options DumpPass# >> /dev/ada0p2 noneswapsw 0 0 >> /dev/ada0p3 / ufs rw 1 1 >> linprocfs /compat/linux/proc linprocfs rw 0 0 >> tmpfs/compat/linux/dev/shm tmpfs rw,mode=17770 >> 0 >> >> >> # df -h >> Filesystem SizeUsed Avail Capacity Mounted on >> /dev/ada0p3428G245G149G62%/ >> devfs 1.0K1.0K 0B 100%/dev >> linprocfs 4.0K4.0K 0B 100%/compat/linux/proc >> tmpfs 47G4.0K 47G 0%/compat/linux/dev/shm >> tmpfs 20M604K 19M 3%/tmp >> >> I don't understand why the /tmp is being mounted. It is causing >> problems >> because when I try to run portupgrade it fails for lack of space. If >> I >> forcibly unmount it everything breaks. >> >> # umount -v /tmp >> umount: unmount of /tmp failed: Device busy >> [root@FreeBSD_13 ~]# umount -vf /tmp >> tmpfs: unmount from /tmp >> [root@FreeBSD_13 ~]# df -h >> Filesystem SizeUsed Avail Capacity Mounted on >> /dev/ada0p3428G245G149G62%/ >> devfs 1.0K1.0K 0B 100%/dev >> linprocfs 4.0K4.0K 0B 100%/compat/linux/proc >> tmpfs 47G4.0K 47G 0%/compat/linux/dev/shm >> [root@FreeBSD_13 ~]# vinagre >> Unable to init server: Could not connect to 127.0.0.1: Connection >> refused >> >> (vinagre:27111): Gtk-WARNING **: 15:04:21.599: cannot open display: >> :0 >> >> Any help would be appreciated, thanks in advance. >> > >The problem isn't that /tmp is tmpfs, the problem is that it's being >mounted by /etc/rc.d/tmp as a 20MB filesystem because tmpsize="20m" is >the default. You could set tmpsize to some bigger value in rc.conf, or >you can add an explicit mount for /tmp in fstab so that you get the >full (47G on your system) capacity that's available: > > tmpfs /tmp tmpfs rw 0 0 > >-- Ian > > >___ >freebsd-current@freebsd.org mailing list >https://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to >"freebsd-current-unsubscr...@freebsd.org" I've seen clients inadvertently DoS themselves when I was a Solaris admin. Solaris never used limits for tmpfs. As to how we arrived at 20m, I recall an OSF/1 course where the instructor intimated that 20m was industry best practice at the time and OSF/1 being BSD. That was a lifetime ago. Maybe it's time to consider a higher default for 2019. Anticipating a memory constrained embedded argument, people designing products would customize it anyway. -- Pardon the typos and autocorrect, small keyboard in use. Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: filesystem mount problem
On Sun, 2019-07-21 at 15:07 -0400, AN wrote: > Hi: > > FreeBSD FreeBSD_13 13.0-CURRENT FreeBSD 13.0-CURRENT #102 r350187: > Sat Jul > 20 19:04:30 EDT 2019 > root@FreeBSD_13:/usr/obj/usr/src/amd64.amd64/sys/MYKERNEL amd64 > 1300036 > > I would appreciate some help with the following problem. > > /etc/fstab: > # Device Mountpoint FStype Options DumpPass# > /dev/ada0p2 noneswapsw 0 0 > /dev/ada0p3 / ufs rw 1 1 > linprocfs /compat/linux/proclinprocfs rw 0 0 > tmpfs/compat/linux/dev/shmtmpfs rw,mode=17770 > 0 > > > # df -h > Filesystem SizeUsed Avail Capacity Mounted on > /dev/ada0p3428G245G149G62%/ > devfs 1.0K1.0K 0B 100%/dev > linprocfs 4.0K4.0K 0B 100%/compat/linux/proc > tmpfs 47G4.0K 47G 0%/compat/linux/dev/shm > tmpfs 20M604K 19M 3%/tmp > > I don't understand why the /tmp is being mounted. It is causing > problems > because when I try to run portupgrade it fails for lack of space. If > I > forcibly unmount it everything breaks. > > # umount -v /tmp > umount: unmount of /tmp failed: Device busy > [root@FreeBSD_13 ~]# umount -vf /tmp > tmpfs: unmount from /tmp > [root@FreeBSD_13 ~]# df -h > Filesystem SizeUsed Avail Capacity Mounted on > /dev/ada0p3428G245G149G62%/ > devfs 1.0K1.0K 0B 100%/dev > linprocfs 4.0K4.0K 0B 100%/compat/linux/proc > tmpfs 47G4.0K 47G 0%/compat/linux/dev/shm > [root@FreeBSD_13 ~]# vinagre > Unable to init server: Could not connect to 127.0.0.1: Connection > refused > > (vinagre:27111): Gtk-WARNING **: 15:04:21.599: cannot open display: > :0 > > Any help would be appreciated, thanks in advance. > The problem isn't that /tmp is tmpfs, the problem is that it's being mounted by /etc/rc.d/tmp as a 20MB filesystem because tmpsize="20m" is the default. You could set tmpsize to some bigger value in rc.conf, or you can add an explicit mount for /tmp in fstab so that you get the full (47G on your system) capacity that's available: tmpfs /tmp tmpfs rw 0 0 -- Ian ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: filesystem mount problem
On Sun, 21 Jul 2019 15:07-0400, AN wrote: > I don't understand why the /tmp is being mounted. It is causing problems > because when I try to run portupgrade it fails for lack of space. If I > forcibly unmount it everything breaks. tmpmfs is set to "AUTO" in /etc/defaults/rc.conf. Try setting tmpmfs="NO" in /etc/rc.conf, reboot, and see if this prohibits the creation of /tmp as a tmpfs. You can also set PKG_TMPDIR or TMPDIR to point to, say, /var/tmp. E.g.: export PKG_TMPDIR=/var/tmp or setenv PKG_TMPDIR /var/tmp > # umount -v /tmp > umount: unmount of /tmp failed: Device busy > [root@FreeBSD_13 ~]# umount -vf /tmp > tmpfs: unmount from /tmp > [root@FreeBSD_13 ~]# df -h > Filesystem SizeUsed Avail Capacity Mounted on > /dev/ada0p3428G245G149G62%/ > devfs 1.0K1.0K 0B 100%/dev > linprocfs 4.0K4.0K 0B 100%/compat/linux/proc > tmpfs 47G4.0K 47G 0%/compat/linux/dev/shm > [root@FreeBSD_13 ~]# vinagre > Unable to init server: Could not connect to 127.0.0.1: Connection refused > > (vinagre:27111): Gtk-WARNING **: 15:04:21.599: cannot open display: :0 This is expected when /tmp/.X11-unix/X0 ceases to exist, among other files within /tmp. -- Trond. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: filesystem mount problem
## AN (a...@neu.net): > tmpfs 47G4.0K 47G 0%/compat/linux/dev/shm > tmpfs 20M604K 19M 3%/tmp > I don't understand why the /tmp is being mounted. It is causing problems > because when I try to run portupgrade it fails for lack of space. If I > forcibly unmount it everything breaks. Either you have set "tmpmfs" in rc.conf to "YES", or your /tmp (before mounting the tmpfs) is not writable (in which case the default "tmpmfs" setting of "AUTO" resorts to mounting the tmpfs). Sset "tmpmfs" to "NO" and make sure you've got a writeable /tmp. See /etc/rc.d/tmp for reference. (The scripts itself seem to not have been changed since 12 or so). Regards, Christoph -- Spare Space ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
