From: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: nikola.ciprich@linuxbox.cz
Subject: BUG: enabling psacct breaks fsfreeze
Date: Tue, 23 Oct 2012 11:43:51 +0200 [thread overview]
Message-ID: <20121023094351.GC27919@pcnci.linuxbox.cz> (raw)
[-- Attachment #1: Type: text/plain, Size: 946 bytes --]
Hi,
while trying to create consistent backups of KVM guest, I've discovered
that fsfreeze always hangs.. deeper investigation revealed psacct to be the culprit.
When psacct is disabled, fsfreeze works fine, when enabled, the command never returns.
I suppose that the problem is /var is not on separate partition (ie it's same volume
as /) and psacct isn't able to dump process exit information about fsfreeze command
thus creating deadlock..
problem is 100% reproducible on both latest 3.0.x kernel and 3.7-r1c.
Should more debugging information be needed, I'll be glad to provide whatever I can..
BR
nik
--
-------------------------------------
Ing. Nikola CIPRICH
LinuxBox.cz, s.r.o.
28.rijna 168, 709 00 Ostrava
tel.: +420 591 166 214
fax: +420 596 621 273
mobil: +420 777 093 799
www.linuxbox.cz
mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2012-10-23 9:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 9:43 Nikola Ciprich [this message]
2012-10-31 12:15 ` BUG: enabling psacct breaks fsfreeze Jan Kara
2012-10-31 12:46 ` Nikola Ciprich
2012-11-01 9:37 ` Jan Kara
2012-11-01 11:19 ` Jan Kara
2012-11-01 14:23 ` Nikola Ciprich
2012-11-01 22:50 ` Jan Kara
2012-11-02 9:50 ` Marco Stornelli
2012-11-02 10:40 ` Nikola Ciprich
2012-11-03 8:22 ` Marco Stornelli
2012-11-07 18:51 ` Jan Kara
2012-11-07 21:21 ` Nikola Ciprich
2012-11-07 22:32 ` Jan Kara
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=20121023094351.GC27919@pcnci.linuxbox.cz \
--to=nikola.ciprich@linuxbox.cz \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).