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
[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
>
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 invo
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
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]:
>
> s
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.o
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
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
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
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. I
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
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
> > do
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 versio
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 -
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 asa
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, chmodd
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
Typo
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
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 "zf
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
20 matches
Mail list logo
