In previous months I had already the same problem with ZFS if
nvidia driver was loaded via /boot/loader.conf. It triggered
the same error. So I loaded the driver on demand with kldload
after login and everything (X + stuff) worked fine.
Very strange...
Does anyone have a clue what is going on
On Monday, October 27, 2014 6:46:17 pm Michael Schmiedgen wrote:
> On 10/27/2014 22:29, Ryan Stone wrote:
> > On Mon, Oct 27, 2014 at 4:21 PM, Michael Schmiedgen
wrote:
> >> Hi List,
> >>
> >> my ZFS does not mount. I bifurcated to r271963 that
> >> does not work anymore. The commit seems not dir
On 10/27/2014 22:29, Ryan Stone wrote:
On Mon, Oct 27, 2014 at 4:21 PM, Michael Schmiedgen wrote:
Hi List,
my ZFS does not mount. I bifurcated to r271963 that
does not work anymore. The commit seems not directly
related to ZFS, but is rather a conversion from timeout(9)
to callout(9).
After b
On Mon, Oct 27, 2014 at 4:21 PM, Michael Schmiedgen wrote:
> Hi List,
>
> my ZFS does not mount. I bifurcated to r271963 that
> does not work anymore. The commit seems not directly
> related to ZFS, but is rather a conversion from timeout(9)
> to callout(9).
>
> After booting the kernel it drops t
Hi List,
my ZFS does not mount. I bifurcated to r271963 that
does not work anymore. The commit seems not directly
related to ZFS, but is rather a conversion from timeout(9)
to callout(9).
After booting the kernel it drops to the mount prompt,
stating that ZFS cannot be mounted because of 'error
