From: dexen deVries <dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Problem report: cannot run nilfs_cleanerd on full filesystem
Date: Mon, 21 Mar 2011 13:05:48 +0100 [thread overview]
Message-ID: <201103211305.48353.dexen.devries@gmail.com> (raw)
In-Reply-To: <20110321.200706.260176646.ryusuke-sG5X7nlA6pw@public.gmane.org>
Hi again,
On Monday 21 of March 2011 12:07:06 you wrote:
> The ".nilfs" file is used for two purposes:
>
> 1) As the file on which the nilfs library issues ioctls.
>
> 2) For advisory locks (i.e. fcntl(F_GETLK/F_SETLK/FSETLKW)). This
> works as a mutex between the cleaner and other nilfs-tools.
Regarding 2), it seems multiple instances of nilfs_cleanerd can be started for
one filesystem (which leads to metadata corruption, as per my earlier
``Regarding problem with nilfs_cleanerd - part 2 and Nilfs_cleanerd err=-17''
mail).
Is that intentional? Should we guard on nilfs_cleanerd level, or on kernel
level?
Regards,
--
dexen deVries
[[[↓][→]]]
``In other news, STFU and hack.''
mahmud, in response to Erann Gat's ``How I lost my faith in Lisp''
http://news.ycombinator.com/item?id=2308816
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-03-21 12:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 16:37 Problem report: cannot run nilfs_cleanerd on full filesystem dexen deVries
[not found] ` <201103191738.00187.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-03-19 22:01 ` Reinoud Zandijk
[not found] ` <20110319220157.GA681-bVHBekiX4bNgoMqBc1r0ESegHCQxtGRMHZ5vskTnxNA@public.gmane.org>
2011-03-19 22:12 ` dexen deVries
[not found] ` <201103192312.38046.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-03-20 12:50 ` Reinoud Zandijk
[not found] ` <20110320125040.GA735-bVHBekiX4bNgoMqBc1r0ESegHCQxtGRMHZ5vskTnxNA@public.gmane.org>
2011-03-21 11:07 ` Ryusuke Konishi
[not found] ` <20110321.200706.260176646.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-03-21 12:00 ` dexen deVries
[not found] ` <201103211300.50177.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-03-21 15:07 ` Ryusuke Konishi
[not found] ` <20110322.000702.112911778.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-03-21 15:30 ` Ryusuke Konishi
2011-03-21 12:05 ` dexen deVries [this message]
[not found] ` <201103211305.48353.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-03-21 15:17 ` Ryusuke Konishi
2011-03-21 13:01 ` Reinoud Zandijk
[not found] ` <20110321130151.GA29111-bVHBekiX4bNgoMqBc1r0ESegHCQxtGRMHZ5vskTnxNA@public.gmane.org>
2011-03-23 7:51 ` Reinoud Zandijk
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=201103211305.48353.dexen.devries@gmail.com \
--to=dexen.devries-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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.