On 04/10/2007, Nathan Kroenert [EMAIL PROTECTED] wrote:
Client A
- import pool make couple-o-changes
Client B
- import pool -f (heh)
Oct 4 15:03:12 fozzie ^Mpanic[cpu0]/thread=ff0002b51c80:
Oct 4 15:03:12 fozzie genunix: [ID 603766 kern.notice] assertion
failed: dmu_read(os,
Dick Davies wrote:
On 04/10/2007, Nathan Kroenert [EMAIL PROTECTED] wrote:
Client A
- import pool make couple-o-changes
Client B
- import pool -f (heh)
Oct 4 15:03:12 fozzie ^Mpanic[cpu0]/thread=ff0002b51c80:
Oct 4 15:03:12 fozzie genunix: [ID 603766 kern.notice]
Wouldn't this be the known feature where a write error to zfs forces a panic?
Vic
On 10/4/07, Ben Rockwood [EMAIL PROTECTED] wrote:
Dick Davies wrote:
On 04/10/2007, Nathan Kroenert [EMAIL PROTECTED] wrote:
Client A
- import pool make couple-o-changes
Client B
- import
I think it's a little more sinister than that...
I'm only just trying to import the pool. Not even yet doing any I/O to it...
Perhaps it's the same cause, I don't know...
But I'm certainly not convinced that I'd be happy with a 25K, for
example, panicing just because I tried to import a dud
Perhaps it's the same cause, I don't know...
But I'm certainly not convinced that I'd be happy with a 25K, for
example, panicing just because I tried to import a dud pool...
I'm ok(ish) with the panic on a failed write to a non-redundant storage.
I expect it by now...
I agree, forcing a
Client A
- import pool make couple-o-changes
Client B
- import pool -f (heh)
Client A + B - With both mounting the same pool, touched a couple of
files, and removed a couple of files from each client
Client A + B - zpool export
Client A - Attempted import and dropped the panic.
On Thu, Oct 04, 2007 at 08:36:10AM -0600, eric kustarz wrote:
Client A
- import pool make couple-o-changes
Client B
- import pool -f (heh)
Client A + B - With both mounting the same pool, touched a couple of
files, and removed a couple of files from each client
Client A +
Erik -
Thanks for that, but I know the pool is corrupted - That was kind if the
point of the exercise.
The bug (at least to me) is ZFS panicing Solaris just trying to import
the dud pool.
But, maybe I'm missing your point?
Nathan.
eric kustarz wrote:
Client A
- import pool make
On Fri, Oct 05, 2007 at 08:20:13AM +1000, Nathan Kroenert wrote:
Erik -
Thanks for that, but I know the pool is corrupted - That was kind if the
point of the exercise.
The bug (at least to me) is ZFS panicing Solaris just trying to import
the dud pool.
But, maybe I'm missing your
Awesome.
Thanks, Eric. :)
This type of feature / fix is quite important to a number of the guys in
the our local OSUG. In particular, they are adamant that they cannot use
ZFS in production until it stops panicing the whole box for isolated
filesystem / zpool failures.
This will be a big
Some people are just dumb. Take me, for instance... :)
Was just looking into ZFS on iscsi and doing some painful and unnatural
things to my boxes and dropped a panic I was not expecting.
Here is what I did.
Server: (S10_u4 sparc)
- zpool create usb /dev/dsk/c4t0d0s0
(on a 4gb USB stick,
11 matches
Mail list logo
