On Sat, 2018-06-30 at 21:11 -0400, David Wysochanski wrote:
> On Fri, 2018-06-29 at 12:04 +0100, Jeremy Harris wrote:
> > On 06/28/2018 11:09 PM, David Wysochanski wrote:
> > > One problem with all of these non-storage location algorithms is that
> > > it won't give you the precise location of the
On Fri, 2018-06-29 at 12:04 +0100, Jeremy Harris wrote:
> On 06/28/2018 11:09 PM, David Wysochanski wrote:
> > One problem with all of these non-storage location algorithms is that
> > it won't give you the precise location of the start of the loop in the
> > list (i.e. the one with the corrupted
On 06/29/2018 11:29 AM, David Mair wrote:
> On 06/26/2018 08:34 AM, Jeremy Harris wrote:
>> On 06/26/2018 03:29 PM, David Wysochanski wrote:
>>> On Tue, 2018-06-26 at 09:21 -0400, Dave Anderson wrote:
Yes, by default all list entries encountered are put in the built-in
hash queue,
On 06/26/2018 08:34 AM, Jeremy Harris wrote:
> On 06/26/2018 03:29 PM, David Wysochanski wrote:
>> On Tue, 2018-06-26 at 09:21 -0400, Dave Anderson wrote:
>>> Yes, by default all list entries encountered are put in the built-in
>>> hash queue, specifically for the purpose of determining whether
On 06/29/2018 05:04 AM, Jeremy Harris wrote:
> On 06/28/2018 11:09 PM, David Wysochanski wrote:
>> One problem with all of these non-storage location algorithms is that
>> it won't give you the precise location of the start of the loop in the
>> list (i.e. the one with the corrupted 'prev' list
On 06/28/2018 11:09 PM, David Wysochanski wrote:
> One problem with all of these non-storage location algorithms is that
> it won't give you the precise location of the start of the loop in the
> list (i.e. the one with the corrupted 'prev' list entry.
>
> I am not sure if this is a show stopper
On Tue, 2018-06-26 at 15:34 +0100, Jeremy Harris wrote:
> On 06/26/2018 03:29 PM, David Wysochanski wrote:
> > On Tue, 2018-06-26 at 09:21 -0400, Dave Anderson wrote:
> > > Yes, by default all list entries encountered are put in the built-in
> > > hash queue, specifically for the purpose of
On Tue, 2018-06-26 at 15:34 +0100, Jeremy Harris wrote:
> On 06/26/2018 03:29 PM, David Wysochanski wrote:
> > On Tue, 2018-06-26 at 09:21 -0400, Dave Anderson wrote:
> > > Yes, by default all list entries encountered are put in the built-in
> > > hash queue, specifically for the purpose of
On 06/27/2018 09:02 AM, David Mair wrote:
> On 06/26/2018 12:01 PM, Dave Kleikamp wrote:
>> On 06/26/2018 11:15 AM, Dave Anderson wrote:
>>>
>>>
>>> - Original Message -
On 06/26/2018 10:40 AM, David Wysochanski wrote:
> On Tue, 2018-06-26 at 11:27 -0400, Dave Anderson wrote:
On 06/26/2018 12:01 PM, Dave Kleikamp wrote:
> On 06/26/2018 11:15 AM, Dave Anderson wrote:
>>
>>
>> - Original Message -
>>> On 06/26/2018 10:40 AM, David Wysochanski wrote:
On Tue, 2018-06-26 at 11:27 -0400, Dave Anderson wrote:
>
> - Original Message -
>> On
- Original Message -
> On Tue, 2018-06-26 at 11:59 -0400, Dave Anderson wrote:
> >
> > - Original Message -
> > > On Tue, 2018-06-26 at 11:27 -0400, Dave Anderson wrote:
> > > >
> > > > - Original Message -
> > > > > On Tue, 2018-06-26 at 15:34 +0100, Jeremy Harris
- Original Message -
> On Tue, 2018-06-26 at 11:59 -0400, Dave Anderson wrote:
> >
> > - Original Message -
> > > On Tue, 2018-06-26 at 11:27 -0400, Dave Anderson wrote:
> > > >
> > > > - Original Message -
> > > > > On Tue, 2018-06-26 at 15:34 +0100, Jeremy Harris
On 06/26/2018 11:15 AM, Dave Anderson wrote:
>
>
> - Original Message -
>> On 06/26/2018 10:40 AM, David Wysochanski wrote:
>>> On Tue, 2018-06-26 at 11:27 -0400, Dave Anderson wrote:
- Original Message -
> On Tue, 2018-06-26 at 15:34 +0100, Jeremy Harris wrote:
On Tue, 2018-06-26 at 11:59 -0400, Dave Anderson wrote:
>
> - Original Message -
> > On Tue, 2018-06-26 at 11:27 -0400, Dave Anderson wrote:
> > >
> > > - Original Message -
> > > > On Tue, 2018-06-26 at 15:34 +0100, Jeremy Harris wrote:
> > > > > On 06/26/2018 03:29 PM, David
- Original Message -
> On 06/26/2018 10:40 AM, David Wysochanski wrote:
> > On Tue, 2018-06-26 at 11:27 -0400, Dave Anderson wrote:
> >>
> >> - Original Message -
> >>> On Tue, 2018-06-26 at 15:34 +0100, Jeremy Harris wrote:
> On 06/26/2018 03:29 PM, David Wysochanski
On 06/26/2018 10:40 AM, David Wysochanski wrote:
> On Tue, 2018-06-26 at 11:27 -0400, Dave Anderson wrote:
>>
>> - Original Message -
>>> On Tue, 2018-06-26 at 15:34 +0100, Jeremy Harris wrote:
On 06/26/2018 03:29 PM, David Wysochanski wrote:
> On Tue, 2018-06-26 at 09:21 -0400,
- Original Message -
> On Tue, 2018-06-26 at 11:27 -0400, Dave Anderson wrote:
> >
> > - Original Message -
> > > On Tue, 2018-06-26 at 15:34 +0100, Jeremy Harris wrote:
> > > > On 06/26/2018 03:29 PM, David Wysochanski wrote:
> > > > > On Tue, 2018-06-26 at 09:21 -0400, Dave
On Tue, 2018-06-26 at 11:27 -0400, Dave Anderson wrote:
>
> - Original Message -
> > On Tue, 2018-06-26 at 15:34 +0100, Jeremy Harris wrote:
> > > On 06/26/2018 03:29 PM, David Wysochanski wrote:
> > > > On Tue, 2018-06-26 at 09:21 -0400, Dave Anderson wrote:
> > > > > Yes, by default all
- Original Message -
> On Tue, 2018-06-26 at 15:34 +0100, Jeremy Harris wrote:
> > On 06/26/2018 03:29 PM, David Wysochanski wrote:
> > > On Tue, 2018-06-26 at 09:21 -0400, Dave Anderson wrote:
> > > > Yes, by default all list entries encountered are put in the built-in
> > > > hash
On Tue, 2018-06-26 at 09:21 -0400, Dave Anderson wrote:
>
> - Original Message -
> > Hi Dave,
> >
> > We have a fairly large vmcore (around 250GB) that has a very long kmem
> > cache we are trying to determine whether a loop exists in it. The list
> > has literally billions of entries.
- Original Message -
> Hi Dave,
>
> We have a fairly large vmcore (around 250GB) that has a very long kmem
> cache we are trying to determine whether a loop exists in it. The list
> has literally billions of entries. Before you roll your eyes hear me
> out.
>
> Just running the
Hi Dave,
We have a fairly large vmcore (around 250GB) that has a very long kmem
cache we are trying to determine whether a loop exists in it. The list
has literally billions of entries. Before you roll your eyes hear me
out.
Just running the following command
crash> list -H 0x8ac03c81fc28
22 matches
Mail list logo