Processing commands for cont...@bugs.debian.org:
> tags 651624 + upstream
Bug #651624 [kfreebsd-image-9-amd64] sometimes device nodes disappear after a
reboot, making
Added tag(s) upstream.
> forwarded 651624 http://www.freebsd.org/cgi/query-pr.cgi?pr=175179
Bug #651624 [kfreebsd-image-9-amd64] s
On 06/01/13 03:58, Steven Chamberlain wrote:
> I think it might have to do with devices in the zpool being renamed [...]
> Furthermore, there is a particular problem when ZFS is on a partition,
> rather than a whole device, and if that partition extends to the end of
> the disk.
> If both ada0 an
El 17 d’abril de 2012 22:07, Christoph Egger ha escrit:
>> Confirmed: the list is empty. The device nodes aren't present.
>> Furthermore, rebooting doesn't help but shutdown fixes the problem.
>>
>> Christoph, I only hit this problem in VirtualBox. Did you experience
>> it with real hardware, al
Robert Millan writes:
> retitle 651624 sometimes device nodes disappear after a reboot, making
> them inaccessible to root file system
> thanks
>
> El 10 d’abril de 2012 17:38, Robert Millan ha escrit:
>> Some tests that could confirm this, when any of us hits the problem again:
>>
>> - When you
retitle 651624 sometimes device nodes disappear after a reboot, making
them inaccessible to root file system
thanks
El 10 d’abril de 2012 17:38, Robert Millan ha escrit:
> Some tests that could confirm this, when any of us hits the problem again:
>
> - When you get the mount error, type "?" in m
Hi,
I suspect this bug has nothing to do with the actual content of the
device. Some hints:
- It recently happened in one of my VMs. Tried rebooting a few
times, always failed. Then instead of reboot I shut down and restart,
then it works. Disk content has to be exactly the same in all test
El 25 de març de 2012 23:07, Christoph Egger ha escrit:
> Robert Millan writes:
>> I'm not sure if people in debian-bsd can help with this. I myself
>> can't. Maybe you should try to reproduce this in a pure FreeBSD
>> environment by trying to import the pool from a FreeBSD system. If it
>> ca
Hi!
Robert Millan writes:
> I'm not sure if people in debian-bsd can help with this. I myself
> can't. Maybe you should try to reproduce this in a pure FreeBSD
> environment by trying to import the pool from a FreeBSD system. If it
> can be imported with kFreeBSD 8.x (either GNU or BSD userlan
El 8 de febrer de 2012 19:16, Christoph Egger ha escrit:
> pool: base
> id: 6831564585978878790
> state: FAULTED
> status: One or more devices contains corrupted data.
> action: The pool cannot be imported due to damaged devices or data.
> The pool may be active on another system, but
Hi!
Just an interesting Gem I noticed. `zpool list -o version` tells me my
pool is at version 28 while `zdb` thinks it's version 15.
Regards
Christoph
--
9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer
--
To UNSUBSCRIBE, email to deb
Hi!
Robert Millan writes:
> El 21 de desembre de 2011 12:23, Christoph Egger
> ha escrit:
>> I've managed to build kfreebsd-9 9.0~svn228246-2 now and using that
>> kernel (cp to /boot) mounts the zfs root while both the stable and the
>> unstable 9.0 kernel do not. Not sure why.
>
> Sounds like
El 21 de desembre de 2011 12:23, Christoph Egger
ha escrit:
> I've managed to build kfreebsd-9 9.0~svn228246-2 now and using that
> kernel (cp to /boot) mounts the zfs root while both the stable and the
> unstable 9.0 kernel do not. Not sure why.
Sounds like heisenbug. Could you try the other t
On Tue, Dec 13, 2011 at 08:06:42AM +0100, Robert Millan wrote:
> 2011/12/12 Christoph Egger :
> >> Please try setting vfs.zfs.debug=1 from GRUB and see if relevant
> >> output turns up.
> >
> > [...]
>
> Can't see anything relevant in those messages. Could you rebuild
> kfreebsd-9 with debug opti
Another test that might be useful is booting from a kfreebsd-9 rescue
image and trying to import your pool from command-line (zpool import
-o altroot=/target base).
If that fails it'll probably give more useful diagnostics.
--
Robert Millan
--
To UNSUBSCRIBE, email to debian-bsd-requ...@list
2011/12/12 Christoph Egger :
>> Please try setting vfs.zfs.debug=1 from GRUB and see if relevant
>> output turns up.
>
> [...]
Can't see anything relevant in those messages. Could you rebuild
kfreebsd-9 with debug options (see attachment) and try that? The
internal sanity checks might bring up s
Robert Millan writes:
> 2011/12/12 Christoph Egger :
>>> Maybe they've fixed this bug recently. I just uploaded a new SVN
>>> snapshot to experimental (9.0~svn228246-1), can you try?
>>
>> Still the same failure.
>
> Please try setting vfs.zfs.debug=1 from GRUB and see if relevant
> output turns
2011/12/12 Christoph Egger :
>> Maybe they've fixed this bug recently. I just uploaded a new SVN
>> snapshot to experimental (9.0~svn228246-1), can you try?
>
> Still the same failure.
Please try setting vfs.zfs.debug=1 from GRUB and see if relevant
output turns up.
--
Robert Millan
--
To UNS
Hi!
On Sun, Dec 11, 2011 at 12:57:45PM +0100, Robert Millan wrote:
> 2011/12/10 Christoph Egger :
> > The official 9.0 kernel manages to mount the root fs
>
> Maybe they've fixed this bug recently. I just uploaded a new SVN
> snapshot to experimental (9.0~svn228246-1), can you try?
Still the sa
2011/12/11 Steven Chamberlain :
> * I managed to install to a new ZFS root under kfreebsd 8.2, upgrade to
> kfreebsd 9 and still boot it; so what did we do differently for
> Christoph to have this issue?
Hard to say. It's probably just not reproducible every time, or
depends on factors that can'
Hi,
On 11/12/11 12:03, Robert Millan wrote:
> Please don't add unrelated information to bug reports. If you found a
> new bug, you can file it, or we can discuss it in the mailing list(s).
Okay sorry, some of that I ought to file separate bugs for, but
regarding this bug I was really trying to s
Hi Steven,
Please don't add unrelated information to bug reports. If you found a
new bug, you can file it, or we can discuss it in the mailing list(s).
I replaced the CC to BTS with debian-bsd.
2011/12/11 Steven Chamberlain :
> which only has kfreebsd-image-8.2-1-amd64 8.2-15 (I guess because
>
2011/12/10 Christoph Egger :
> The official 9.0 kernel manages to mount the root fs
Maybe they've fixed this bug recently. I just uploaded a new SVN
snapshot to experimental (9.0~svn228246-1), can you try?
--
Robert Millan
--
To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org
with
On 10/12/11 16:52, Christoph Egger wrote:
> Booting from a zfs root filesystem (created with the daily installer
> and a 8.2 kernel) fails with the kfreebsd 9 kernel
Hi,
I just had a go at this myself and it worked. I had trouble with
zfsutils during install though which may be relevant.
I used
2011/12/10 Christoph Egger :
> Setting up kfreebsd-downloader (9.0~rc2-1) ...
> --2011-12-10 18:40:14--
> http://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/9.0-RC2/kernel.txz
> Resolving ftp.freebsd.org (ftp.freebsd.org)... 2001:6c8:2:600::132,
> 2001:4f8:0:2::e, 149.20.64.73, ...
> Connec
Hi!
Christoph Egger writes:
> Robert Millan writes:
>> Can you reproduce this with upstream kernel? (kfreebsd-downloader).
>> If it's an upstream bug, it'd help to get upstream involved IMHO.
>
> trying to use a bootonly iso via netvoot also failed. will continue
> trying stuff.
The official 9.
Hi!
Robert Millan writes:
> Can you reproduce this with upstream kernel? (kfreebsd-downloader).
> If it's an upstream bug, it'd help to get upstream involved IMHO.
Unfortunately the downloader doesn't work any more as rc3 is released:
Setting up kfreebsd-downloader (9.0~rc2-1) ...
--2011-12-10
2011/12/10 Christoph Egger :
> Booting from a zfs root filesystem (created with the daily installer
> and a 8.2 kernel) fails with the kfreebsd 9 kernel: kfreebsd can mount
> a root filesystem and the kernel drops in the manual root filesystem
> selection dialog. This happens both, with the 8.2 st
Package: kfreebsd-image-9-amd64
Version: 9.0~svn227451-6
Severity: important
Hi!
Booting from a zfs root filesystem (created with the daily installer
and a 8.2 kernel) fails with the kfreebsd 9 kernel: kfreebsd can mount
a root filesystem and the kernel drops in the manual root filesystem
selec
28 matches
Mail list logo
