On Wednesday, 29 December 2010, jhell wrote:
>
> Another note too, I think I read that you mentioned using the L2ARC and
> slog device on the same disk You simply shouldn't do this it could
> be contributing to the real cause and there is absolutely no gain in
> either sanity or performance a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/28/2010 18:20, Martin Matuska wrote:
> Please don't consider these patches as production-ready.
> What we want to do is find and resolve as many bugs as possible.
I completely agree with Martin here. If your running it then your
willing to loose
Hi
On Wednesday, 29 December 2010, Martin Matuska wrote:
> Please don't consider these patches as production-ready.
> What we want to do is find and resolve as many bugs as possible.
>
> To help us fix these bugs, a way to reproduce the bug from a clean start
> (e.g. in virtualbox) would be great
Please don't consider these patches as production-ready.
What we want to do is find and resolve as many bugs as possible.
To help us fix these bugs, a way to reproduce the bug from a clean start
(e.g. in virtualbox) would be great and speed up finding the cause for
the problem.
Your problem looks
On Tue, Dec 28, 2010 at 9:39 AM, Jean-Yves Avenard
> Now, I haven't tried using cache and log from a different disk. The
> motherboard on the server has 8 SATA ports, and I have no free port to
> add another disk. So my only option to have both a log and cache
> device in my zfs pool, is to use two
On 29 December 2010 03:15, Jean-Yves Avenard wrote:
> # zpool import
> load: 0.00 cmd: zpool 405 [spa_namespace_lock] 15.11r 0.00u 0.03s 0% 2556k
> load: 0.00 cmd: zpool 405 [spa_namespace_lock] 15.94r 0.00u 0.03s 0% 2556k
> load: 0.00 cmd: zpool 405 [spa_namespace_lock] 16.57r 0.00u 0.03s 0%
Hi
On 27 December 2010 16:04, jhell wrote:
> 1) Set vfs.zfs.recover=1 at the loader prompt (OK set vfs.zfs.recover=1)
> 2) Boot into single user mode without opensolaris.ko and zfs.ko loaded
> 3) ( mount -w / ) to make sure you can remove and also write new
> zpool.cache as needed.
> 3) Remove /
Hi
On 27 December 2010 16:04, jhell wrote:
>
> Before anything else can you: (in FreeBSD)
>
> 1) Set vfs.zfs.recover=1 at the loader prompt (OK set vfs.zfs.recover=1)
> 2) Boot into single user mode without opensolaris.ko and zfs.ko loaded
> 3) ( mount -w / ) to make sure you can remove and also
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/26/2010 23:17, Jean-Yves Avenard wrote:
> Responding to myself again :P
>
> On 27 December 2010 13:28, Jean-Yves Avenard wrote:
>> tried to force a zpool import
>>
>> got a kernel panic:
>> panic: solaris assert: weight >= space && weight <= 2
Responding to myself again :P
On 27 December 2010 13:28, Jean-Yves Avenard wrote:
> tried to force a zpool import
>
> got a kernel panic:
> panic: solaris assert: weight >= space && weight <= 2 * space, file:
> /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/metaslab.c,
tried to force a zpool import
got a kernel panic:
panic: solaris assert: weight >= space && weight <= 2 * space, file:
/usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/metaslab.c,
line: 793
cpuid = 5
KDB: stack backtrace
#0: 0xff805f64be at kdb_backtrace
#1 .. pa
11 matches
Mail list logo
