On Mon, Oct 31, 2011 at 9:07 AM, Jim Klimov wrote:
> 2011-10-31 16:28, Paul Kraus wrote:
>> Oracle has provided a loaner system with 128 GB RAM and it took 75 GB of
>> RAM
>> to destroy the problem snapshot). I had not yet posted a summary as we
>> are still working through the overall problem (w
2011-10-31 16:28, Paul Kraus wrote:
How big is / was the snapshot and dataset ? I am dealing with a 7
TB dataset and a 2.5 TB snapshot on a system with 32 GB RAM.
I had a smaller-scale problem, with datasets and snapshots sized
several hundred GB, but on an 8Gb RAM system. So proportionall
On Sun, Oct 30, 2011 at 5:13 PM, Jim Klimov wrote:
>> I know there was (is ?) a bug where a zfs destroy of a large
>> snapshot would run a system out of kernel memory, but searching the
> Symptoms are like what you've described, including the huge scanrate
> just before the system dies (becom
2011-10-31 1:13, Jim Klimov пишет:
Sorry, I am late.
...
If my memory and GoogleCache don't fail me too much, I ended
up with the following incantations for pool-import attempts:
:; echo zfs_vdev_max_pending/W0t5 | mdb -kw
:; echo "aok/W 1" | mdb -kw
:; echo "zfs_recover/W 1" | mdb -kw
:; echo
I know there was (is ?) a bug where a zfs destroy of a large
snapshot would run a system out of kernel memory, but searching the
list archives and on defects.opensolaris.org I cannot find it. Could
someone here explain the failure mechanism in language a Sys Admin (I
am NOT a developer) could
On Thu, Sep 15, 2011 at 1:20 AM, Daniel Carosone wrote:
> Can you import it booting from a newer kernel (say liveDVD), and allow
> that to complete the deletion?
I have not tried anything newer than the latest patched 5.10.
> Or does this not help until the pool is
> upgraded past the on-disk f
On Wed, Sep 14, 2011 at 05:36:53PM -0400, Paul Kraus wrote:
> T2000 with 32 GB RAM
>
> zpool that hangs the machine by running it out of kernel memory when
> trying to import the zpool
>
> zpool has an "incomplete" snapshot from a zfs recv that it is trying
> to destroy on import
>
> I *can* imp
On Wed, Sep 14, 2011 at 4:31 PM, Richard Elling
wrote:
>> From watching the system try to import this pool, it looks like it is
>> still building a kernel structure in RAM when the system runs out of
>> RAM. It has not committed anything to disk.
>
> Did you experience a severe memory shortfall?
Question below…
On Sep 14, 2011, at 12:07 PM, Paul Kraus wrote:
> On Wed, Sep 14, 2011 at 2:30 PM, Richard Elling
> wrote:
>
>> I don't recall a bug with that description. However, there are several bugs
>> that
>> relate to how the internals work that were fixed last summer and led to the
>>
On Wed, Sep 14, 2011 at 2:30 PM, Richard Elling
wrote:
> I don't recall a bug with that description. However, there are several bugs
> that
> relate to how the internals work that were fixed last summer and led to the
> on-disk format change to version 26 (Improved snapshot deletion performance)
On Sep 14, 2011, at 9:50 AM, Paul Kraus wrote:
>I know there was (is ?) a bug where a zfs destroy of a large
> snapshot would run a system out of kernel memory, but searching the
> list archives and on defects.opensolaris.org I cannot find it. Could
> someone here explain the failure mechanism
I know there was (is ?) a bug where a zfs destroy of a large
snapshot would run a system out of kernel memory, but searching the
list archives and on defects.opensolaris.org I cannot find it. Could
someone here explain the failure mechanism in language a Sys Admin (I
am NOT a developer) could u
12 matches
Mail list logo
