Date: Mon, 28 Jan 2008 11:33:34 +0100 From: J H <jh2007554@s6.sector6.net> To: Richard Todd <RMTodd@ichotolot.servalan.com> Cc: Pawel Jakub Dawidek <pjd@FreeBSD.org>, freebsd-stable@freebsd.org Subject: Re: "ad0: TIMEOUT - WRITE_DMA" type errors with 7.0-RC1 Message-ID: <479DAF7E.20303@s6.sector6.net> In-Reply-To: <x7sl0l3zo3.fsf@ichotolot.servalan.com> References: <479A0731.6020405@skyrush.com> <20080125162940.GA38494@eos.sc1.parodius.com> <479A3764.6050800@skyrush.com> <3803988D-8D18-4E89-92EA-19BF62FD2395@mac.com> <479A4CB0.5080206@skyrush.com> <20080126003845.GA52183@eos.sc1.parodius.com> <20080126010054.GA52891@eos.sc1.parodius.com> <20080126010653.GA53255@eos.sc1.parodius.com> <479A8A24.5050409@skyrush.com> <x7sl0l3zo3.fsf@ichotolot.servalan.com>
index | next in thread | previous in thread | raw e-mail
Richard Todd wrote:
> Workaround: always make sure you run /etc/rc.d/hostid start in single-user before doing any ZFS tinkering.
>
Good advice -- thank you.
But it still sounds like Jeremy's assessment, "it's a bug", is
accurate. ZFS could certainly check for zero hostid. If zero, it
should /definitely/ display a diagnostic which encourages the admin to
use /etc/rc.d/hostid (or a printout of it). If zero, it /might/
additionally do some reads in case a likely-looking /etc/rc.d/hostid is
available, and display the hostid, perhaps even speculatively start
using it. It would save some needless "no datasets available" hair pulling.
Cheers,
JH
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?479DAF7E.20303>