From: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
To: Marco Stornelli <marco.stornelli@gmail.com>
Cc: Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Nikola Ciprich <nikola.ciprich@linuxbox.cz>
Subject: Re: BUG: enabling psacct breaks fsfreeze
Date: Fri, 2 Nov 2012 11:40:18 +0100 [thread overview]
Message-ID: <20121102104018.GG20752@pcnci.linuxbox.cz> (raw)
In-Reply-To: <5093977A.9010507@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 873 bytes --]
> I saw this behavior (task-hang) when I tested the fsfreeze code. I was
> writing a little patch to replace fsfreeze's wait queue with a killable
> queue, in this way the user can do at least "kill -9", but since the
> behavior was the same before your patch I didn't send it. I don't know if we
> can break any previous behavior. The funny thing here is that it's like if
> fsfreeze freezes itself :)
I think freezing all tasks ain't that bad, my problem is it's not possible to
start fsfreeze -u to thaw filesystem..
>
> Marco
>
--
-------------------------------------
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 prev parent reply other threads:[~2012-11-02 10:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 9:43 BUG: enabling psacct breaks fsfreeze Nikola Ciprich
2012-10-31 12:15 ` 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 [this message]
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=20121102104018.GG20752@pcnci.linuxbox.cz \
--to=nikola.ciprich@linuxbox.cz \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.stornelli@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.