Re: Deadlock in md barrier code? / RAID1 / LVM CoW snapshot + ext3 / Debian 5.0 - lenny 2.6.26 kernel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 18 Oct 2010 19:52:36 +0100
Tim Small <tim@xxxxxxxxxxx> wrote:

> Neil Brown wrote:
> > Maybe if you can get me a full sysrq-T list that might help.
> >    
> 
> At last, yes, courtesy of Ben Hutchings...
> 
> http://buttersideup.com/files/md-raid1-lockup-lvm-snapshot/deadlock-openvz-2.6.26-Debian5.txt

Thanks!

> 
> ... any use?

Only in as much as that it excludes some possible avenues of investigation,
which has some value.

But I'm out of ideas.  I cannot think of anything that could keep
->nr_pending or ->barrier elevated such that raise_barrier would
block for a long time.

Maybe you could try adding printks to print
  conf->{barrier,nr_pending,nr_waiting,nr_queued}
just before and after the second wait_event_lock_irq in raise_barrier().

That might help...

NeilBrown




> 
> Cheers,
> 
> Tim.
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux