From: Gene Heskett <gene.heskett@verizon.net>
To: linux-kernel@vger.kernel.org
Cc: Gildas LE NADAN <gildas.le-nadan@inha.fr>
Subject: Re: unkillable processes using samba, xfs and lvm2 snapshots (k 2.6.10)
Date: Tue, 28 Dec 2004 09:07:01 -0500 [thread overview]
Message-ID: <200412280907.01681.gene.heskett@verizon.net> (raw)
In-Reply-To: <41D14251.4030704@inha.fr>
On Tuesday 28 December 2004 06:24, Gildas LE NADAN wrote:
>Hi,
>
>I experience hangs on samba processes on a filer using xfs over lvm2
> as data partitions, when there is active snapshots of the xfs
> partitions.
>
>I have a clone of the production server (same software, same
> hardware) where the situation can be reproduced perfectly.
>
>Testings showed that the result was the same, whether the snapshots
> were mounted or not : smbd processes are locked and unkillable
> while the machine is normaly working otherwise, except software
> reboot is impossible and hardware reset is needed.
>
>I noticed Brad Fitzpatrick's case in kernel 2.6.10 changelog
>(http://lkml.org/lkml/2004/11/14/98) and tested kernel 2.6.10 today
>without success.
>
>Configuration is the following :
>- supermicro m/b with dual Xeon 2,8Ghz (SMT is active)
>- 1 GB ram,
>- adaptec u320 raid controler
>- kernel 2.6.10
>- debian sarge
>- samba 3
>- LVM2
>- XFS with quota turned on
>
>All software are from debian sarge packages, except the kernel.
>
>I'm not able to determine if the problem is more xfs, device mapper
> or samba related, and was not able to do extensive testings (using
> a different filesystem, testing with a different daemon, etc...),
> but SMT/SMP testings showed that this is not a SMP/SMT related
> problem.
>
>I've compiled the kernel with the debugging options, so I might
> provide additional informations if needed as in Brad's case.
>
>Sincerely,
>Gildas LE NADAN
>(Please CC me as I didn't suscribe to LKML)
I have a somewhat similar case here, samba processses are unkillable,
but I can do a software reboot. Something is also killing amandad,
and I lost the backup of this machine last night. The amanda logs
are bereft of any info and I've no clue that its happened except a
message from amanda that the client access timed out on this machine.
This was while running 2.6.10-rc3-mm1-V0.33-04 which ran stably for 8
days previously.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.30% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
next prev parent reply other threads:[~2004-12-28 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 11:24 Gildas LE NADAN
2004-12-28 11:39 ` bert hubert
2004-12-28 15:15 ` unkillable processes using samba, xfs and lvm2 snapshots (k 2.6.10) [includes backtrace] Gildas LE NADAN
2004-12-28 14:07 ` Gene Heskett [this message]
2005-01-02 12:41 ` unkillable processes using samba, xfs and lvm2 snapshots (k 2.6.10) Christian Leber
2004-12-29 18:01 ` Julien BLACHE
2005-01-05 11:37 ` Christoph Hellwig
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=200412280907.01681.gene.heskett@verizon.net \
--to=gene.heskett@verizon.net \
--cc=gildas.le-nadan@inha.fr \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®