linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Bear Wolf <sportbear@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] new process dead after create multiple snapshot volumes
Date: Mon, 19 Sep 2005 09:35:09 +0800	[thread overview]
Message-ID: <95bbd1905091818351226a9ec@mail.gmail.com> (raw)
In-Reply-To: <20050917191609.GE12882@barkeeper1.linbit>

Thank you Ellenberg.
now I learn more things..^_^

should I put this at Redhat Bugzila?
because it's always reproducible with RH-FC3,

"demsetup resume target &" still not work..

2005/9/18, Lars Ellenberg <Lars.Ellenberg@linbit.com>:
> / 2005-09-17 14:27:10 +0800
> it is not "dead", it is in "uninteruptible sleep".
> that is a big difference.
> 
> yes, those are the kernel threads responsible for the sync.
> there are initially two of them per cpu.
> if they (try to) sync to some device mapper target which is suspended,
> they themselves get suspended.
> this can hang the system: no io possible, nothing possible
> anymore that needs io...
> 
> > -bash-3.00# ps x
> >   PID TTY      STAT   TIME COMMAND
> >     1 ?        S      0:01 init [2]
> >     2 ?        S      0:00 [migration/0]
> >     3 ?        SN     0:00 [ksoftirqd/0]
> >     4 ?        S<     0:00 [events/0]
> >     5 ?        S<     0:00 [khelper]
> >     6 ?        S<     0:00 [kthread]
> >     8 ?        S<     0:00 [kacpid]
> >    70 ?        S<     0:00 [kblockd/0]
> >    73 ?        S<     0:00 [khubd]
> >   129 ?        S      0:00 [pdflush]
> >   130 ?        D      0:00 [pdflush]
> >   132 ?        S<     0:00 [aio/0]
> >   131 ?        S      0:00 [kswapd0]
> >   134 ?        S<     0:00 [xfslogd/0]
> >   133 ?        S      0:00 [cifsoplockd]
> >   135 ?        S<     0:00 [xfsdatad/0]
> >   136 ?        S      0:00 [xfsbufd]
> >   723 ?        S<     0:00 [kseriod]
> >   773 ?        S      0:00 [scsi_eh_0]
> >   777 ?        S<     0:00 [ata/0]
> >   801 ?        S<     0:00 [kcryptd/0]
> >   934 ?        S<     0:00 [kcopyd]
> >  1330 ?        Ss     0:00 syslogd -m 0
> >  1334 ?        Ss     0:00 klogd -x
> >  1343 ?        Ss     0:00 /usr/httpd/bin/httpd
> >  1353 ?        Ss     0:00 crond
> >  1359 ?        Ss     0:00 /bin/profamd
> >  1479 tty1     Ss     0:00 -bash
> >  1481 tty2     Ss+    0:00 -bash
> >  1483 tty3     Ss+    0:00 /sbin/mingetty tty3
> >  1485 tty4     Ss+    0:00 /sbin/mingetty tty4
> >  1487 tty5     Ss+    0:00 /sbin/mingetty tty5
> >  1903 ?        S      0:00 [xfssyncd]
> >  1915 tty1     D+     0:00 sync
> >  2037 pts/0    R+     0:00 ps x
> 
> --
> : Lars Ellenberg                                  Tel +43-1-8178292-0  :
> : LINBIT Information Technologies GmbH            Fax +43-1-8178292-82 :
> : Schoenbrunner Str. 244, A-1120 Vienna/Europe   http://www.linbit.com :
>

      reply	other threads:[~2005-09-19  1:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-12  2:34 [linux-lvm] new process dead after create multiple snapshot volumes Bear Wolf
2005-09-12  8:05 ` Lars Ellenberg
2005-09-12  8:42   ` Bear Wolf
2005-09-17  6:27     ` Bear Wolf
2005-09-17  8:23       ` Bear Wolf
2005-09-17  8:31         ` Bear Wolf
2005-09-17 19:16       ` Lars Ellenberg
2005-09-19  1:35         ` Bear Wolf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=95bbd1905091818351226a9ec@mail.gmail.com \
    --to=sportbear@gmail.com \
    --cc=linux-lvm@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).