total configured swap pages exceeds maximum recommended amount
I am not subscribed to -stable, so please keep me CC'd. I am CC'ing folks who have touched this code or dealt with it recently or in the past. Something has changed regarding how FreeBSD determines when to emit this message. I do not know if this is a regression. The message below comes from a stable/11 r330260 amd64 box w/ 8GB RAM and 32GB swap during boot: warning: total configured swap (8358563 pages) exceeds maximum recommended amount (8141112 pages). warning: increase kern.maxswzone or reduce amount of swap. In stable/9, the message could be squelched via kern.maxswzone="0" in loader.conf. Confirmation is here (see Dag-Erling's responses): https://lists.freebsd.org/pipermail/freebsd-stable/2012-August/069301.html In stable/11, this no longer appears to work (the default value is 0). The reason this box has 32GB swap (4x more than existing RAM) has to do with planning ahead. The system can support up to 32GB RAM, but does not have all the DIMM slots populated at this time. Swap on this machine is a physical partition on its main disk, thus "shrinking swap" is not not possible without a full format/reinstall. This code has been touched/tweaked semi-recently in PR 221356: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221356 Code references: stable/9: https://svnweb.freebsd.org/base/stable/9/sys/vm/swap_pager.c?annotate=284100#l2132 stable/10: https://svnweb.freebsd.org/base/stable/10/sys/vm/swap_pager.c?annotate=320557#l2156 stable/11: https://svnweb.freebsd.org/base/stable/11/sys/vm/swap_pager.c?annotate=329591#l2126 My questions: how does one squelch this warning message on such systems running stable/11? If it involves setting the tunable to a more useful value, how does one reliably calculate that value? Thank you. -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: total configured swap pages exceeds maximum recommended amount
[Recipient list trimmed, as this response addresses a peripheral consern -- dhw] On Fri, Mar 02, 2018 at 12:23:34AM -0800, Jeremy Chadwick wrote: > ... > The reason this box has 32GB swap (4x more than existing RAM) has to do > with planning ahead. The system can support up to 32GB RAM, but does > not have all the DIMM slots populated at this time. Swap on this > machine is a physical partition on its main disk, thus "shrinking swap" > is not not possible without a full format/reinstall. > . Actually, now that you have sized the partitions. you could use "gpart resize" to shrink the (effective) swap partition, leaving a "hole" (of unused diske space) -- for now. Later, you could use "gpart resize" again to reclaim (some of) the unused space for your swap partition, should you want to do so. Peace, david -- David H. Wolfskill da...@catwhisker.org Yes, the indictments don't "prove" guilt; that's what trials are for. See http://www.catwhisker.org/~david/publickey.gpg for my public key. signature.asc Description: PGP signature
Re: [CFT] [X11] graphics/drm-next-kmod now builds, loads and works on FreeBSD-11-stable
On Sun, 18 Feb 2018 21:35:24 +0100 Hans Petter Selasky wrote: > Hi FreeBSD desktop users! > > During the past week and over the weekend all parts needed for building, > loading and using graphics/drm-next-kmod on FreeBSD-11-stable have been > completed! > Thanks for the hard work by all involved! Tested a few days ago, reported in the forum post here: https://forums.freebsd.org/threads/using-drm-next-kmod-on-freebsd-11-stable.64731/#post-378702 TL;DR - it works on a Toshiba Satellite Z30-B-10W (Broadwell-U, Intel HD Graphics 5500). One issue - the text console (before starting Xorg) has serious lag, you can type a command before anything shows on the screen. Should I open an issue for this on Github? HTH -- Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
recent 11.1-stable oddness
Hello stable@ Over the last few weeks, I've noticed the following new behaviours from 11.1 stable [only took note of the revision from the last update which was r330243 unfortunately as I thought it was my config/fault initially]: shutdown -r now no longer works as it did (ie: shutdown and reboot). What happens now is that it gets to: "syncing disks, vnodes remaining...5 5 5 4 0 0 0 done All buffers synced Swap device [file] removed. <-- there is no swapfile installed! Uptime: (whatever the uptime was) ukbd0: detached ums0: detached uhid0: detached uhub6: detached ukbd1: detached uhub3: detached umass0: detached uhub0: detached ...and there it sits until a hard reset via the power button is applied. Reboot and poweroff still work as one would expect. also, why is it talking about a swapfile? There is a swap partition but no swapfile: # swapinfo Device 1K-blocks UsedAvail Capacity /dev/ada0s1b 39745800 3974580 0% # swapctl -l Device: 1024-blocks Used: /dev/ada0s1b3974580 0 # cat /etc/fstab # DeviceMountpoint FStype Options DumpPass# /dev/ada0s1a/ ufs rw 1 1 /dev/ada0s1bnoneswapsw 0 0 linprocfs /compat/linux/proc linprocfs rw 0 0 tmpfs/compat/linux/dev/shm tmpfs rw,mode=17770 0 fdescfs /dev/fd fdescfs rw,late 0 0 any ideas? thanks, - J. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: recent 11.1-stable oddness
On Fri, Mar 2, 2018 at 10:15 AM, tech-lists wrote: > Hello stable@ > > Over the last few weeks, I've noticed the following new behaviours from > 11.1 stable [only took note of the revision from the last update which > was r330243 unfortunately as I thought it was my config/fault initially]: > > shutdown -r now no longer works as it did (ie: shutdown and reboot). > What happens now is that it gets to: > > "syncing disks, vnodes remaining...5 5 5 4 0 0 0 done > All buffers synced > Swap device [file] removed. <-- there is no swapfile installed! > Uptime: (whatever the uptime was) > ukbd0: detached > ums0: detached > uhid0: detached > uhub6: detached > ukbd1: detached > uhub3: detached > umass0: detached > uhub0: detached > > ...and there it sits until a hard reset via the power button is applied. > If you set hw.usb.no_shutdown_wait to 1 via sysctl, does it shutdown/reboot normally? -- Freddie Cash fjwc...@gmail.com ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: recent 11.1-stable oddness
On 02/03/2018 18:29, Freddie Cash wrote: > If you set hw.usb.no_shutdown_wait to 1 via sysctl, does it > shutdown/reboot normally? thanks for the tip. I'll try it and let you know -- J. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: recent 11.1-stable oddness
On 02/03/2018 18:29, Freddie Cash wrote: > If you set hw.usb.no_shutdown_wait to 1 via sysctl, does it > shutdown/reboot normally? > yes it does! Many thanks. -- J. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [CFT] [X11] graphics/drm-next-kmod now builds, loads and works on FreeBSD-11-stable
On 3/2/18 7:53 AM, Torfinn Ingolfsen wrote: > On Sun, 18 Feb 2018 21:35:24 +0100 > Hans Petter Selasky wrote: > >> Hi FreeBSD desktop users! >> >> During the past week and over the weekend all parts needed for building, >> loading and using graphics/drm-next-kmod on FreeBSD-11-stable have been >> completed! >> > Thanks for the hard work by all involved! > > Tested a few days ago, reported in the forum post here: > https://forums.freebsd.org/threads/using-drm-next-kmod-on-freebsd-11-stable.64731/#post-378702 > TL;DR - it works on a Toshiba Satellite Z30-B-10W (Broadwell-U, Intel HD > Graphics 5500). One issue - the text console (before starting Xorg) has > serious lag, > you can type a command before anything shows on the screen. Should I open an > issue for this on Github? > HTH Hey there - thanks for testing! I would recommend posting an issue on the Github repo for this. If you could be sure to include which revision you are running (11-stable or 12-current revision) in addition to the version of the port/pkg you have install that'd be helpful. Cheers, -pete -- Pete Wright p...@nomadlogic.org 310.309.9298 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
zfs problems after rebuilding system
Hi, Importing two zpools after a hd crash, the first pool I imported auto-loads at boot. But the second one I'm always having to zfs mount (zpool name) then mount the zfs subdirs. The system was like this: ada0 (this had the OS on. It was replaced after it crashed. Not a member of any zpool, not zfs at all, no root-on-zfs). New freebsd-11-stable-snapshot was installed to this disk. ada1 \ ada2 -- these made up zpool0, a raidz pool. Each device is a 1TB disk. ada3 / zpool1 - this is striped, one 4TB disk, attached via usb3 zpool1/c - this is compressed with lz4 zpool1/important - this has copies=2 enabled I ran zpool import zpool0 and then zpool import zpool1 and both imported without error. However despite setting the mountpoint for zpool1 as /zpool1, on reboot I always have to: # zfs mount zpool1 or I won't see the drive in df -h or mount or zfs mount. But I *will* find it at its mountpoint /zpool1. If I do a ls -lah on that, I can see zpool1/c and zpool1/important as dirs but not in zfs mount or (normal) mount, nor can I see the other dirs that are not vdevs. If I then zfs mount zpool1 I can see all the dirs and vdevs on that disk off its root, in ls -lah. But I dont see the vdevs in zfs mount. I have to zfs mount zpool1/c and zfs mount zpool1/important to see the vdevs in zfs mount. Confusingly, I didn't need to and don't have to do any of that for zpool0. What am I doing wrong/what am I missing? Why is zpool0 automatically loading but zpool1 is not? Before ada0 (the failed disk) was replaced, both loaded on boot. thanks, -- J. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: zfs problems after rebuilding system
On Fri, Mar 2, 2018 at 1:25 PM, tech-lists wrote: > Hi, > > Importing two zpools after a hd crash, the first pool I imported > auto-loads at boot. But the second one I'm always having to zfs mount > (zpool name) then mount the zfs subdirs. The system was like this: > > ada0 (this had the OS on. It was replaced after it crashed. Not a member > of any zpool, not zfs at all, no root-on-zfs). New > freebsd-11-stable-snapshot was installed to this disk. > > ada1 \ > ada2 -- these made up zpool0, a raidz pool. Each device is a 1TB disk. > ada3 / > > zpool1 - this is striped, one 4TB disk, attached via usb3 > > zpool1/c - this is compressed with lz4 > zpool1/important - this has copies=2 enabled > > I ran zpool import zpool0 and then zpool import zpool1 and both imported > without error. However despite setting the mountpoint for zpool1 as > /zpool1, on reboot I always have to: > > # zfs mount zpool1 > > or I won't see the drive in df -h or mount or zfs mount. > > But I *will* find it at its mountpoint /zpool1. If I do a ls -lah on > that, I can see zpool1/c and zpool1/important as dirs but not in zfs > mount or (normal) mount, nor can I see the other dirs that are not vdevs. > > If I then zfs mount zpool1 I can see all the dirs and vdevs on that disk > off its root, in ls -lah. But I dont see the vdevs in zfs mount. I have > to zfs mount zpool1/c and zfs mount zpool1/important to see the vdevs in > zfs mount. > This doesn't make sense. vdevs have nothing to do with mounting. You see your vdevs by doing "zpool status". What are you expecting to see that you don't? > > Confusingly, I didn't need to and don't have to do any of that for > zpool0. What am I doing wrong/what am I missing? Why is zpool0 > automatically loading but zpool1 is not? Before ada0 (the failed disk) > was replaced, both loaded on boot. > Please post the output of "zfs list -r -o name,mountpoint,canmount,mounted" and also the contents of /etc/fstab. Also, have you set "zfs_enable=YES" in /etc/rc.conf? -Alan ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: zfs problems after rebuilding system
Hi, thanks for looking at this, On 02/03/2018 20:39, Alan Somers wrote: > This doesn't make sense. vdevs have nothing to do with mounting. You see > your vdevs by doing "zpool status". What are you expecting to see that you > don't? sorry, I was confusing terms. I was expecting to see similar to output of zfs list from both zpools instead of just zpool0. (just rebooted the system.) OK here's zpool status: # zpool status pool: zpool1 state: ONLINE scan: scrub repaired 0 in 0h39m with 0 errors on Mon Feb 5 22:55:31 2018 config: NAMESTATE READ WRITE CKSUM zpool1 ONLINE 0 0 0 diskid/DISK-NA7DKXXF ONLINE 0 0 0 errors: No known data errors pool: zpool0 state: ONLINE scan: scrub repaired 0 in 3h46m with 0 errors on Thu Mar 1 23:01:29 2018 config: NAMESTATE READ WRITE CKSUM zpool0 ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 ada1ONLINE 0 0 0 ada2ONLINE 0 0 0 ada3ONLINE 0 0 0 > >> Confusingly, I didn't need to and don't have to do any of that for >> zpool0. What am I doing wrong/what am I missing? Why is zpool0 >> automatically loading but zpool1 is not? Before ada0 (the failed disk) >> was replaced, both loaded on boot. >> > Please post the output of "zfs list -r -o name,mountpoint,canmount,mounted" > and also the contents of /etc/fstab. # zfs list -r -o name,mountpoint,canmount,mounted NAME MOUNTPOINT CANMOUNT MOUNTED zpool1 /zpool1 on no zpool1/compressed/zpool1/compressedon no zpool1/important /zpool1/important on no zpool0 /zpool0 on yes zpool0/home /zpool0/home on yes zpool0/usr /zpool0/usr on yes zpool0/usr/local /zpool0/usr/local on yes zpool0/usr/oldsrc/usr/oldsrc on yes zpool0/usr/ports /usr/portson yes zpool0/usr/src /usr/src on yes zpool0/vms /zpool0/vms on yes # cat /etc/fstab # DeviceMountpoint FStype Options DumpPass# /dev/ada0s1a/ ufs rw 1 1 /dev/ada0s1bnoneswapsw 0 0 linprocfs /compat/linux/proc linprocfs rw 0 0 tmpfs/compat/linux/dev/shm tmpfs rw,mode=17770 0 fdescfs /dev/fd fdescfs rw,late 0 0 > Also, have you set "zfs_enable=YES" in /etc/rc.conf? yes. If I run zfs mount -a, everything zfs is mounted as expected. I'm wondering if at bootup, when zfs mount is called (I suppose it must be called from somewhere), whether it needs to specify -a. I would not know the first place to look though. thanks, -- J. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: zfs problems after rebuilding system
On Fri, Mar 2, 2018 at 2:26 PM, tech-lists wrote: > Hi, thanks for looking at this, > > On 02/03/2018 20:39, Alan Somers wrote: > > This doesn't make sense. vdevs have nothing to do with mounting. You > see > > your vdevs by doing "zpool status". What are you expecting to see that > you > > don't? > > sorry, I was confusing terms. I was expecting to see similar to output > of zfs list from both zpools instead of just zpool0. > > (just rebooted the system.) > > OK here's zpool status: > > # zpool status > pool: zpool1 > state: ONLINE > scan: scrub repaired 0 in 0h39m with 0 errors on Mon Feb 5 22:55:31 2018 > config: > > NAMESTATE READ WRITE CKSUM > zpool1 ONLINE 0 0 0 > diskid/DISK-NA7DKXXF ONLINE 0 0 0 > > errors: No known data errors > > pool: zpool0 > state: ONLINE > scan: scrub repaired 0 in 3h46m with 0 errors on Thu Mar 1 23:01:29 2018 > config: > > NAMESTATE READ WRITE CKSUM > zpool0 ONLINE 0 0 0 > raidz1-0 ONLINE 0 0 0 > ada1ONLINE 0 0 0 > ada2ONLINE 0 0 0 > ada3ONLINE 0 0 0 > > > >> Confusingly, I didn't need to and don't have to do any of that for > >> zpool0. What am I doing wrong/what am I missing? Why is zpool0 > >> automatically loading but zpool1 is not? Before ada0 (the failed disk) > >> was replaced, both loaded on boot. > >> > > Please post the output of "zfs list -r -o name,mountpoint,canmount, > mounted" > > and also the contents of /etc/fstab. > > # zfs list -r -o name,mountpoint,canmount,mounted > NAME MOUNTPOINT CANMOUNT MOUNTED > zpool1 /zpool1 on no > zpool1/compressed/zpool1/compressedon no > zpool1/important /zpool1/important on no > zpool0 /zpool0 on yes > zpool0/home /zpool0/home on yes > zpool0/usr /zpool0/usr on yes > zpool0/usr/local /zpool0/usr/local on yes > zpool0/usr/oldsrc/usr/oldsrc on yes > zpool0/usr/ports /usr/portson yes > zpool0/usr/src /usr/src on yes > zpool0/vms /zpool0/vms on yes > > # cat /etc/fstab > # DeviceMountpoint FStype Options DumpPass# > /dev/ada0s1a/ ufs rw 1 1 > /dev/ada0s1bnoneswapsw 0 0 > linprocfs /compat/linux/proc linprocfs rw 0 0 > tmpfs/compat/linux/dev/shm tmpfs rw,mode=17770 0 > fdescfs /dev/fd fdescfs rw,late 0 0 > > > Also, have you set "zfs_enable=YES" in /etc/rc.conf? > > yes. > > If I run zfs mount -a, everything zfs is mounted as expected. I'm > wondering if at bootup, when zfs mount is called (I suppose it must be > called from somewhere), whether it needs to specify -a. I would not know > the first place to look though. > The relevant code is in /etc/rc.d/zfs, and it already uses "-a". Have you checked if /etc/rc.d/zfs is printing any errors to the console during boot? -Alan ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: zfs problems after rebuilding system
On 02/03/2018 21:38, Alan Somers wrote: > The relevant code is in /etc/rc.d/zfs, and it already uses "-a". Have > you checked if /etc/rc.d/zfs is printing any errors to the console > during boot? Nothing much in dmesg -a # dmesg -a | egrep -i zfs ZFS filesystem version: 5 ZFS storage pool version: features support (5000) # cat /etc/rc.conf | egrep -i zfs zfs_enable="YES" very puzzling -- J. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: zfs problems after rebuilding system
On Fri, Mar 2, 2018 at 2:53 PM, tech-lists wrote: > On 02/03/2018 21:38, Alan Somers wrote: > > The relevant code is in /etc/rc.d/zfs, and it already uses "-a". Have > > you checked if /etc/rc.d/zfs is printing any errors to the console > > during boot? > > Nothing much in dmesg -a > > # dmesg -a | egrep -i zfs > ZFS filesystem version: 5 > ZFS storage pool version: features support (5000) > > # cat /etc/rc.conf | egrep -i zfs > zfs_enable="YES" > > very puzzling > -- > J. > dmesg only shows stuff that comes from the kernel, not the console. To see what's printed to the console, you'll actually have to watch it. Or enable /var/log/console.log by uncommenting the appropriate line in /etc/syslog.conf. -Alan ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: zfs problems after rebuilding system
On 02/03/2018 21:56, Alan Somers wrote: > dmesg only shows stuff that comes from the kernel, not the console. To see > what's printed to the console, you'll actually have to watch it. Or enable > /var/log/console.log by uncommenting the appropriate line in > /etc/syslog.conf. ok will do this asap, thanks -- J. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: zfs problems after rebuilding system
On 02/03/2018 21:56, Alan Somers wrote: > dmesg only shows stuff that comes from the kernel, not the console. To > see what's printed to the console, you'll actually have to watch it. Or > enable /var/log/console.log by uncommenting the appropriate line in > /etc/syslog.conf. ok did that, chmodded it to 600 then gave a kill -1 to its process id, then rebooted. # cat /var/log/console.log | grep -i zfs # lots of info if I less the file, but nothing about zfs here's output of mount: # mount /dev/ada0s1a on / (ufs, local, journaled soft-updates) devfs on /dev (devfs, local, multilabel) linprocfs on /compat/linux/proc (linprocfs, local) tmpfs on /compat/linux/dev/shm (tmpfs, local) zpool0 on /zpool0 (zfs, local, nfsv4acls) zpool0/home on /zpool0/home (zfs, local, nfsv4acls) zpool0/usr on /zpool0/usr (zfs, local, nfsv4acls) zpool0/usr/local on /zpool0/usr/local (zfs, local, nfsv4acls) zpool0/vms on /zpool0/vms (zfs, local, nfsv4acls) zpool0/usr/oldsrc on /usr/oldsrc (zfs, local, nfsv4acls) zpool0/usr/ports on /usr/ports (zfs, local, nfsv4acls) zpool0/usr/src on /usr/src (zfs, local, nfsv4acls) # output of zfs mount # zfs mount zpool0 /zpool0 zpool0/home/zpool0/home zpool0/usr /zpool0/usr zpool0/usr/local /zpool0/usr/local zpool0/vms /zpool0/vms zpool0/usr/oldsrc /usr/oldsrc zpool0/usr/ports /usr/ports zpool0/usr/src /usr/src now I'll do zfs mount -a and then zfs mount # zfs mount -a # zfs mount zpool0 /zpool0 zpool0/home/zpool0/home zpool0/usr /zpool0/usr zpool0/usr/local /zpool0/usr/local zpool0/vms /zpool0/vms zpool0/usr/oldsrc /usr/oldsrc zpool0/usr/ports /usr/ports zpool0/usr/src /usr/src zpool1 /zpool1 zpool1/compressed /zpool1/compressed zpool1/important /zpool1/important and everything is there as it should be, after zfs mount -a. it's as if the /etc/rc.d/zfs either isn't running or I don't know, failing to run the main section, where it uses -av rather than just -a. Is this file the only one that's called to load zfs? I mean, in that file, zfs mount is never called without a parameter. To me, it doesn't look like the file is being run at all. thanks, -- J. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: zfs problems after rebuilding system
You said it's an external USB drive, correct? Could it be a race condition during the boot process where the USB mass storage driver hasn't detected the drive yet when /etc/rc.d/zfs is run? As a test, add a "sleep 30" in that script before the "zfs mount -a" call and reboot. Cheers, Freddie Typos courtesy of my phone. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: zfs problems after rebuilding system
On 3 Mar 2018, at 01:09, Freddie Cash wrote:
>
> You said it's an external USB drive, correct? Could it be a race condition
> during the boot process where the USB mass storage driver hasn't detected
> the drive yet when /etc/rc.d/zfs is run?
>
> As a test, add a "sleep 30" in that script before the "zfs mount -a" call
> and reboot.
Indeed. I have had the following for a few years now, due to USB drives
with ZFS pools:
--- /usr/src/etc/rc.d/zfs 2016-11-08 10:21:29.820131000 +0100
+++ /etc/rc.d/zfs 2016-11-08 12:49:52.971161000 +0100
@@ -25,6 +25,8 @@
zfs_start_main()
{
+ echo "Sleeping for 10 seconds to let USB devices settle..."
+ sleep 10
zfs mount -va
zfs share -a
if [ ! -r /etc/zfs/exports ]; then
For some reason, USB3 (xhci) controllers can take a very, very long time
to correctly attach mass storage devices: I usually see many timeouts
before they finally get detected. After that, the devices always work
just fine, though.
Whether this is due to some sort of BIOS handover trouble, or due to
cheap and/or crappy USB-to-SATA bridges (even with brand WD and Seagate
disks!), I have no idea. I attempted to debug it at some point, but
a well-placed "sleep 10" was an acceptable workaround... :)
-Dimitry
signature.asc
Description: Message signed with OpenPGP
Re: zfs problems after rebuilding system
On 03/03/2018 00:09, Freddie Cash wrote: > You said it's an external USB drive, correct? Could it be a race condition > during the boot process where the USB mass storage driver hasn't detected > the drive yet when /etc/rc.d/zfs is run? > > As a test, add a "sleep 30" in that script before the "zfs mount -a" call > and reboot. Yes it's an external usb3 drive. That's interesting and I'll test that tomorrow. I recently commented out a GENERIC kernel the USB debug line because the console was filling up with usb attach messages on boot. They were appearing after the login prompt. I have a couple of usb3 hubs attached and the disk is attached through one such hub. (although it was done this way because sometimes it'd be seen as /dev/da0 and others as /dev/da4. And possibly linked to this, when it came up as /dev/da0 it was always with a usb2 speed rather than usb3). thanks everyone for your input. -- J. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: NFS 4.1 RECLAIM_COMPLETE FS failed error in combination with ESXi client
NAGY Andreas wrote: >I am trying to get a FreeBSD NFS 4.1 export working with VMware Esxi 6.5u1, >but >it is always mounted as read only. > >After some research, I found out that this is a known problem, and there are >>threads about this from 2015 also in the mailinglist archive. > >As it seems VMware will not change the bahvior of there NFS 4.1 client I >wanted >to ask here if there is a patch or workaround for this available. I believe the attached small patch deals with the ReclaimComplete issue. However, someone else who tested this had additional issues with the mount: - The client logged a couple of things (that sounded weird to me;-) - Something about Readdir seeing directories change too much.. - Something about "wrong reason for not issuing a delegation"... (I don't what either of these are caused by or whether they result in serious breakage of the mount.) They also ran into a hang when transferring a large file. It sounded to me like something that might be a network interface device driver issue and I suggested they disable TSO, LRO and jumbo frames, but I never heard back from them, so I don't know more about this. So, feel free to test with the attached patch and if you run into problems with the mount, email w.r.t. what they are. If we persevere we might get it going ok. rick [stuff snipped] reclaimcom2.patch Description: reclaimcom2.patch ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
