From: Piotr Szymaniak <szarpaj-TbOm9Ca2r9GrDJvtcaxF/A@public.gmane.org>
To: Ryusuke Konishi
<konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
Cc: dexen deVries
<dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: nilfs_cleanerd won't start for root filesystem
Date: Thu, 2 Aug 2012 11:23:06 +0200 [thread overview]
Message-ID: <20120802092306.GV1478@wloczykij> (raw)
In-Reply-To: <20120801.203417.104482564.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 775 bytes --]
On Wed, Aug 01, 2012 at 08:34:17PM +0900, Ryusuke Konishi wrote:
> *snip*
>
> How about the following workaround?
>
> # ln -s /dev/<your-root-partition> /lib/udev/devices/root
> # reboot
My udev installation is missing /lib/udev/devices dir. Maybe that's also
distribution specific?
As a workaround I just modified my cleanerd starter script [1] to check
if /dev/root exists and, if it is missing, create proper /dev/root symlink
to ${TARGETDISK} before nilfs_cleanerd is started.
PS Is there some "proper" way to start nilfs_cleanerd on rootfs? Or
every way is good as far as it works fine? (my solution is missing the
gcpid=foo)
[1] http://www.mail-archive.com/linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org/msg01195.html
Piotr Szymaniak.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-08-02 9:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 7:21 nilfs_cleanerd won't start for root filesystem dexen deVries
2012-08-01 9:00 ` Piotr Szymaniak
2012-08-01 9:32 ` dexen deVries
2012-08-01 11:19 ` Piotr Szymaniak
2012-08-01 11:34 ` Ryusuke Konishi
[not found] ` <20120801.203417.104482564.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2012-08-02 9:23 ` Piotr Szymaniak [this message]
2012-08-02 9:51 ` Ryusuke Konishi
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=20120802092306.GV1478@wloczykij \
--to=szarpaj-tbom9ca2r9grdjvtcaxf/a@public.gmane.org \
--cc=dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@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.