FreeBSD 13.0-BETA2: Xorg slow
I have successfully upgraded the FreeBSD (actually NomadBSD) installed on a Lenovo ThinkPad T450 from 12.2-RELEASE-p3. After upgrading all packages I have replaced the package graphics/drm-fbsd12-kmod with graphics/drm-fbsd13-kmod. After rebooting the laptop works but the Xorg server is slow because it uses a lot of CPU: moving a window around the screen uses 100% of the CPU. Regards, Maurizio ___ 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: iSCSI booting with isboot
Il 06/09/2018 08:34, O'Connor, Daniel ha scritto: On 6 Sep 2018, at 10:18, O'Connor, Daniel wrote: BootNIC: em0 Configure: IPv6 by NIC0 CHAP Type: No CHAP Attempting to login to iSCSI target and scan all LUNs. soreceive BHS is not complete do login failed The last two lines repeat many times (interspersed with other probe/boot messages) until I get to mount root. I did some tcpdumping and it seems that there is iSCSI traffic but it stops and I am wondering if the ethernet card isn't getting tickled correctly so after a while it stops talking. The traffic seems to be... - 3 x NOP In - Read LBA 0 - Login - TUR - Read LBA 0 - Read LBA 0x40 - Read LBA 0x1 - Read LBA 0x641 The reads seem OK and have plausible data (MBR headers) The last thing it sees are 3 x NOP In just after it looks like something (in the kernel!) reads /etc/services which seems pretty weird.. -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum ___ 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" Please try the patch at: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227313 -- Maurizio ___ 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: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted
2018-05-30 17:50 GMT+02:00 Glen Barber : > Hi, > > Could folks please help boot-test the most recent 12.0-CURRENT amd64 > memstick images on various hardware? Note, this is not a request to > install 12.0-CURRENT, only a boot-test with various system knobs > tweaked. > > The most recent images are available at: > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO- > IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-mini-memstick.img > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO- > IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-memstick.img > > We are interested in testing both UEFI and CSM/BIOS/legacy mode, as we > would like to get this included in the upcoming 11.2-RELEASE if the > change that had been committed addresses several boot issues reported > recently. > > Please help test, and report back (both successes and failures). > > Thanks, > > Glen > > Hi, successfully tested the memstick.img on: Mac mini Mid 2011, BIOS and UEFI Desktop based on Asus H81M-K mainboard, BIOS and UEFI -- Maurizio ___ 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: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted
2018-05-30 17:50 GMT+02:00 Glen Barber : > Hi, > > Could folks please help boot-test the most recent 12.0-CURRENT amd64 > memstick images on various hardware? Note, this is not a request to > install 12.0-CURRENT, only a boot-test with various system knobs > tweaked. > > The most recent images are available at: > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO- > IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-mini-memstick.img > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO- > IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-memstick.img > > We are interested in testing both UEFI and CSM/BIOS/legacy mode, as we > would like to get this included in the upcoming 11.2-RELEASE if the > change that had been committed addresses several boot issues reported > recently. > > Please help test, and report back (both successes and failures). > > Thanks, > > Glen > > Hi, successfully tested the memstick.img on: HP Microserver Gen8, BIOS Samsung NP270E5E laptop, BIOS and UEFI -- Maurizio ___ 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"
Cosmetic bug in TOP(1) on i386
Running: # uname -a FreeBSD qbic 11.1-RELEASE-p1 FreeBSD 11.1-RELEASE-p1 #0: Wed Aug 9 11:17:49 UTC 2017 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 after some minutes running top, I can read: last pid: 853; load averages: 0.01, 0.09, 0.07 up 0+00:08:18 14:38:05 27 processes: 1 running, 26 sleeping CPU: 0.0% user, 0.0% nice, 2.2% system, 0.8% interrupt, 97.0% idle Mem: 24M Active, 3980K Inact, 79M Wired, 3137M Free ARC: 36M Total, 17M MFU, 18M MRU, 149K Anon, 870K Header, 800K Other 21쿿20mpressed, 352M Uncompressed, 16.94:1 Ratio Swap: Seconds to delay: PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 839 root 1 20 0 7328K 2160K CPU0 0 0:00 0.04% top where the second ARC line is corrupted. Pressing Ctrl-L corrects the ARC lines. ___ 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"
In FreeBSD 11.1-BETA2/BETA3 VirtualBox bridged network doesn't work
Upgrading from 11.0-RELEASE-p9 to FreeBSD 11.1-BETA2 and now to 11.2-BETA3, the VirtualBox bridged network doesn't work. -- Regards Maurizio ___ 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"
FreeBSD 11.1-BETA2 VirtualBox bridged network doesn't work
Upgrading from # uname -a FreeBSD clover-nas3 11.0-RELEASE-p9 FreeBSD 11.0-RELEASE-p9 #0: Tue Apr 11 08:48:40 UTC 2017 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 # freebsd-version -ku 11.0-RELEASE-p9 11.0-RELEASE-p10 with the latest packages to FreeBSD 11.1-BETA2, with the latest packages, the VirtualBox bridged network doesn't work. -- Regards Maurizio ___ 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"
ssh error: Fssh_packet_write_poll: Connection to 192.168.0.5 port 22: Cannot allocate memory
Hi, while copying some data with sysutils/zrep between computers on the same LAN I have received theis error: 16:09:32382G pool2tb/misc/virtualbox@2016-05-10_07.59.00--14d 16:09:33383G pool2tb/misc/virtualbox@2016-05-10_07.59.00--14d *Fssh_packet_write_poll: Connection to 192.168.0.5 port 22: Cannot allocate memory* WARNING: Removing all zrep configs and snapshots from pool2tb/misc (for TAG=zrep) Continuing in 10 seconds Destroying any zrep-related snapshots from pool2tb/misc Removing zrep-related properties from pool2tb/misc Error: Error transferring pool2tb/misc@zrep_00 to clover-nas3:pool2tb/misc. Resetting The zrep command is: # zrep init pool2tb/misc clover-nas3 pool2tb/misc and the script issues the command: "zfs send -v -R pool2tb/misc@zrep_00 | ssh clover-nas3 zfs recv -F pool2tb/misc" The error is reproducible or, at least, I have obtained it with 3 consequential transfers. The server is running: # uname -a FreeBSD clover-nas2 10.3-RELEASE-p2 FreeBSD 10.3-RELEASE-p2 #0: Wed May 4 06:03:51 UTC 2016 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 Any idea ? Thanks -- Maurizio ___ 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: help with partitioning - huge stripesize
Il 12/10/2015 13:46, Marko Cupać ha scritto: Hi, I've got HP ProLiant DL320g5p server with HP Smart Array E200 RAID controller and 4X300Gb SAS disks. I'd like to use it for hosting jails on ZFS, but no matter how I create zpool, I always get a warning about non-native block size: block size: 8192B configured, 1048576B native I know it is optimal for ZFS to have direct access to disks, but HP Smart Array E200 apparently does not support JBOD mode. I tried to configure both single RAID-5 logical volume and four RAID-0 logical volumes, in both cases diskinfo gives me the following: 512 # sectorsize 299966445568# mediasize in bytes (279G) 585871964 # mediasize in sectors 1048576 # stripesize 643072 # stripeoffset 71798 # Cylinders according to firmware. 255 # Heads according to firmware. 32 # Sectors according to firmware. PA6C90R9SXK07P # Disk ident. With hardware I have, is it better to create single RAID-5 logical volume in HP Smart Array E200 and let ZFS think it deals with single physical drive, or four RAID-0 logical volumes and let ZFS think it deals with four physical drives? Can I just ignore warning about non-native block size? If not, how can I make it go away? Thank you in advance, Hi, in my HP ProLiant Microserver Gen8, via BIOS, is possible to disable the Dynamic HP Smart Array B120i RAID Support and enable the SATA AHCI Support. ZFS works as expected and the block size is correct. Regards, Maurizio ___ 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: Error upgrading from 10.1-RELEASE to 10.2-RELEASE
Il 24/08/2015 14:14, Bjoern A. Zeeb ha scritto: On 24 Aug 2015, at 09:56 , Maurizio Vairani maurizio.vair...@cloverinformatica.it wrote: Hi, I am trying to update an amd64 system. With the command: # freebsd-update upgrade -r 10.2-RELEASE I receive the error: 95101952019530195401955019560195701958019590 done. Applying patches... done. Fetching 13651 files... 1ae3b1c9f35d65ced43103718a87a4201f4e3434160114a0d355bbf5284da6aa has incorrect hash. Note: running # freebsd-update fetch I receive this message: The following files are affected by updates, but no changes have been downloaded because the files have been modified locally: /var/db/mergemaster.mtree but I do not know if it is related to the error above. please see the thread “freebsd-update to 10.2-RELEASE broken ?” on this mailing list from this month; I think there is no solution yet. https://lists.freebsd.org/pipermail/freebsd-stable/2015-August/thread.html#83086 Thank you very much for the link. I have successfully upgraded the system running multiple times (five or six) the command: # freebsd-update -s update2.freebsd.org -r 10.2-RELEASE upgrade until the above error message disappears. Maurizio ___ 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
Error upgrading from 10.1-RELEASE to 10.2-RELEASE
Hi, I am trying to update an amd64 system. With the command: # freebsd-update upgrade -r 10.2-RELEASE I receive the error: 95101952019530195401955019560195701958019590 done. Applying patches... done. Fetching 13651 files... 1ae3b1c9f35d65ced43103718a87a4201f4e3434160114a0d355bbf5284da6aa has incorrect hash. Note: running # freebsd-update fetch I receive this message: The following files are affected by updates, but no changes have been downloaded because the files have been modified locally: /var/db/mergemaster.mtree but I do not know if it is related to the error above. Thanks Maurizio ___ 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: Boot problem if a ZFS log device is missing
On 30/08/2013 12.46, Andriy Gapon wrote: on 30/08/2013 13:37 Andriy Gapon said the following: on 30/08/2013 00:38 Charles Sprickman said the following: If one is willing to accept that data is lost (like the log device is totally smoked), is there a way to boot knowing that you may have some data loss, or is the only option to boot alternate media and force a pool import (assuming that works without the log device)? I think it's the latter. I am not aware of any way to select a behavior similar to import -m or import -F during boot. Perhaps... ZFS_IMPORT_MISSING_LOG should be a default behavior for a root pool or maybe the behavior could be controllable by a tunable. Maurizio, you might want to try the following patch as an interim solution for your environment: --- a/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/spa.c +++ b/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/spa.c @@ -4112,6 +4112,7 @@ spa_import_rootpool(const char *name) } spa-spa_is_root = B_TRUE; spa-spa_import_flags = ZFS_IMPORT_VERBATIM; + spa-spa_import_flags |= ZFS_IMPORT_MISSING_LOG; /* XXX make tunable */ /* * Build up a vdev tree based on the boot device's label config. HI all, unfortunately the patch don't works. The laptop returns the same error message: Mounting from zfs:tank0 failed with error 6 and the same mountroot prompt. I am available for further testing if needs. Thanks anyway, Maurizio ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Boot problem if a ZFS log device is missing
On 29/08/2013 11.01, Andriy Gapon wrote: on 29/08/2013 11:27 Maurizio Vairani said the following: I am able to boot the PC without a cache device but not without a log device. Why ? The log could potentially contain uncommitted entries. Without the log device there is no knowing if it did or did not. And if it did then the pool is inconsistent state without the log device and so it can not be imported. The cache is not persistent and so there is nothing needed from it upon a boot. Thank you for the clear and concise reply. Yesterday I have done some test. If I remove the stick from the USB port, before the shutdown the PC, it don't crash but continues to works. Then I am able to reboot the laptop without inserting the stick with a pool that works in degraded mode. From the end user point of view a PC should always boot, even with a missing ZFS log device. Regards Maurizio ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Boot problem if a ZFS log device is missing
On 30/08/2013 13.45, Ronald Klop wrote: On Fri, 30 Aug 2013 12:58:29 +0200, Johan Hendriks joh.hendr...@gmail.com wrote: Maurizio Vairani wrote: On 29/08/2013 11.01, Andriy Gapon wrote: on 29/08/2013 11:27 Maurizio Vairani said the following: I am able to boot the PC without a cache device but not without a log device. Why ? The log could potentially contain uncommitted entries. Without the log device there is no knowing if it did or did not. And if it did then the pool is inconsistent state without the log device and so it can not be imported. The cache is not persistent and so there is nothing needed from it upon a boot. Thank you for the clear and concise reply. Yesterday I have done some test. If I remove the stick from the USB port, before the shutdown the PC, it don't crash but continues to works. Then I am able to reboot the laptop without inserting the stick with a pool that works in degraded mode. From the end user point of view a PC should always boot, even with a missing ZFS log device. Regards Maurizio ___ freebsd...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-fs To unsubscribe, send any mail to freebsd-fs-unsubscr...@freebsd.org I do not agree with the following. From the end user point of view a PC should always boot, even with a missing ZFS log device. I think it should give you a option to import the pool or not import the pool! No problem I agree, a step in the right direction. There could be a situation when you are not sure that the ZIL is commited, in that situation it would be handy if you can suspend the boot and make sure the ZIL is there when you reboot or import after you attached the ZIL. I would hate it when it corrups my data just because we always import. with or without the ZIL. In your test you remove the ZIL, and when you reboot then it imports correctly, as far as my knowledge goes this is ok, because when the pool is exported there is no left data in the ZIL, it was not there when we exported, so we can import even without the missing ZIL without problem. I think he was just lucky his system wasn't writing a lot to the ZIL at the moment of removal. So his system was in a consistent state. Otherwise you just miss data which is in the ZIL and not on disk. I have removed the stick when there isn't R/W to the disk. BTW: Not everything goes through the ZIL. It is not the same as a journal. Only sync writes go to the ZIL. If you don't use databases or NFS or other software which wants to make sure data is on stable storage, you might rarely use the ZIL. Thanks for the explanation. Ronald. regards Johan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org Regards Maurizio ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Boot problem if a ZFS log device is missing
Hi all, I am using an USB memory stick as cache and log devices for a HDD ZFS pool named tank0: $ zpool status -v tank0 pool: tank0 state: ONLINE scan: scrub repaired 0 in 7h19m with 0 errors on Tue Jul 30 06:11:23 2013 config: NAME STATE READ WRITE CKSUM tank0ONLINE 0 0 0 ada0s1dONLINE 0 0 0 logs gpt/SLOG ONLINE 0 0 0 cache gpt/L2ARC ONLINE 0 0 0 errors: No known data errors If I remove the stick before booting the laptop (a Compaq Presario) it will not boot with the error message: Mounting from zfs:tank0 failed with error 6 end the mountroot prompt is displayed. I need to reinsert the stick to completing the boot process before restarting the laptop. It is possible to boots the laptop without stick if I remove the log device with the command: # zpool remove tank0 gpt/SLOG before switching it off. The pool will works in degraded mode because the cache device is missing, but it works. I am able to boot the PC without a cache device but not without a log device. Why ? The laptop is updated to 9.2-PRERELEASE r254783. Regards Maurizio ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: [SOLVED] Re: Shutdown problem with an USB memory stick as ZFS cache device
On 24/07/2013 13.19, Ronald Klop wrote: On Thu, 18 Jul 2013 09:52:13 +0200, Maurizio Vairani maurizio.vair...@cloverinformatica.it wrote: On 17/07/2013 17:29, Julian H. Stacey wrote: Maurizio Vairani wrote: On 17/07/2013 11:50, Ronald Klop wrote: On Wed, 17 Jul 2013 10:27:09 +0200, Maurizio Vairani maurizio.vair...@cloverinformatica.it wrote: Hi all, on a Compaq Presario laptop I have just installed the latest stable #uname -a FreeBSD presario 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #0: Tue Jul 16 16:32:39 CEST 2013 root@presario:/usr/obj/usr/src/sys/GENERIC amd64 For speed up the compilation I have added to the pool, tank0, a SanDisk memory stick as cache device with the command: # zpool add tank0 cache /dev/da0 But when I shutdown the laptop the process will halt with this screen shot: http://www.dump-it.fr/freebsd-screen-shot/2f9169f18c7c77e52e873580f9c2d4bf.jpg.html and I need to press the power button for more than 4 seconds to switch off the laptop. The problem is always reproducible. Does sysctl hw.usb.no_shutdown_wait=1 help? Ronald. Thank you Ronald it works ! In /boot/loader.conf added the line hw.usb.no_shutdown_wait=1 Maurizio I wonder (from ignorance as I dont use ZFS yet), if that merely masks the symptom or cures the fault ? Presumably one should use a ZFS command to disassociate whatever might have the cache open ? (in case something might need to be written out from cache, if it was a writeable cache ?) I too had a USB shutdown problem (non ZFS, now solved) several people made useful comments on shutdown scripts etc, so I'm cross referencing: http://lists.freebsd.org/pipermail/freebsd-mobile/2013-July/012803.html Cheers, Julian Probably it masks the symptom. Andriy Gapon hypothesizes a bug in the ZFS clean up code: http://lists.freebsd.org/pipermail/freebsd-fs/2013-July/017857.html Surely one can use a startup script with the command: zpool add tank0 cache /dev/da0 and a shutdown script with: zpool remove tank0 /dev/da0 but this mask the symptom too. I prefer the Ronald solution because: - is simpler: it adds only one line (hw.usb.no_shutdown_wait=1) to one file (/boot/loader.conf). - is fastest: the zpool add/remove commands take time and “hw.usb.no_shutdown_wait=1” in /boot/loader.conf speeds up the shutdown process. - is cleaner: the zpool add/remove commands pair will fill up the tank0 pool history. Regards Maurizio Keep an eye on this commit when it is merged to 9-stable. http://svnweb.freebsd.org/changeset/base/253606 It might be the fix of the problem. Ronald. It works ! Just upgraded the laptop to r254783. Shutdown and reboot works fine, regardless of the hw.usb.no_shutdown_wait value. Thanks Maurizio ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: [SOLVED] Re: Shutdown problem with an USB memory stick as ZFS cache device
On 17/07/2013 17:29, Julian H. Stacey wrote: Maurizio Vairani wrote: On 17/07/2013 11:50, Ronald Klop wrote: On Wed, 17 Jul 2013 10:27:09 +0200, Maurizio Vairani maurizio.vair...@cloverinformatica.it wrote: Hi all, on a Compaq Presario laptop I have just installed the latest stable #uname -a FreeBSD presario 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #0: Tue Jul 16 16:32:39 CEST 2013 root@presario:/usr/obj/usr/src/sys/GENERIC amd64 For speed up the compilation I have added to the pool, tank0, a SanDisk memory stick as cache device with the command: # zpool add tank0 cache /dev/da0 But when I shutdown the laptop the process will halt with this screen shot: http://www.dump-it.fr/freebsd-screen-shot/2f9169f18c7c77e52e873580f9c2d4bf.jpg.html and I need to press the power button for more than 4 seconds to switch off the laptop. The problem is always reproducible. Does sysctl hw.usb.no_shutdown_wait=1 help? Ronald. Thank you Ronald it works ! In /boot/loader.conf added the line hw.usb.no_shutdown_wait=1 Maurizio I wonder (from ignorance as I dont use ZFS yet), if that merely masks the symptom or cures the fault ? Presumably one should use a ZFS command to disassociate whatever might have the cache open ? (in case something might need to be written out from cache, if it was a writeable cache ?) I too had a USB shutdown problem (non ZFS, now solved) several people made useful comments on shutdown scripts etc, so I'm cross referencing: http://lists.freebsd.org/pipermail/freebsd-mobile/2013-July/012803.html Cheers, Julian Probably it masks the symptom. Andriy Gapon hypothesizes a bug in the ZFS clean up code: http://lists.freebsd.org/pipermail/freebsd-fs/2013-July/017857.html Surely one can use a startup script with the command: zpool add tank0 cache /dev/da0 and a shutdown script with: zpool remove tank0 /dev/da0 but this mask the symptom too. I prefer the Ronald solution because: - is simpler: it adds only one line (hw.usb.no_shutdown_wait=1) to one file (/boot/loader.conf). - is fastest: the zpool add/remove commands take time and “hw.usb.no_shutdown_wait=1” in /boot/loader.conf speeds up the shutdown process. - is cleaner: the zpool add/remove commands pair will fill up the tank0 pool history. Regards Maurizio ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Shutdown problem with an USB memory stick as ZFS cache device
Hi all, on a Compaq Presario laptop I have just installed the latest stable #uname -a FreeBSD presario 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #0: Tue Jul 16 16:32:39 CEST 2013 root@presario:/usr/obj/usr/src/sys/GENERIC amd64 For speed up the compilation I have added to the pool, tank0, a SanDisk memory stick as cache device with the command: # zpool add tank0 cache /dev/da0 But when I shutdown the laptop the process will halt with this screen shot: http://www.dump-it.fr/freebsd-screen-shot/2f9169f18c7c77e52e873580f9c2d4bf.jpg.html and I need to press the power button for more than 4 seconds to switch off the laptop. The problem is always reproducible. Regards Maurizio ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[SOLVED] Re: Shutdown problem with an USB memory stick as ZFS cache device
On 17/07/2013 11:50, Ronald Klop wrote: On Wed, 17 Jul 2013 10:27:09 +0200, Maurizio Vairani maurizio.vair...@cloverinformatica.it wrote: Hi all, on a Compaq Presario laptop I have just installed the latest stable #uname -a FreeBSD presario 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #0: Tue Jul 16 16:32:39 CEST 2013 root@presario:/usr/obj/usr/src/sys/GENERIC amd64 For speed up the compilation I have added to the pool, tank0, a SanDisk memory stick as cache device with the command: # zpool add tank0 cache /dev/da0 But when I shutdown the laptop the process will halt with this screen shot: http://www.dump-it.fr/freebsd-screen-shot/2f9169f18c7c77e52e873580f9c2d4bf.jpg.html and I need to press the power button for more than 4 seconds to switch off the laptop. The problem is always reproducible. Does sysctl hw.usb.no_shutdown_wait=1 help? Ronald. Thank you Ronald it works ! In /boot/loader.conf added the line hw.usb.no_shutdown_wait=1 Maurizio ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
