Linux NILFS development
 help / color / mirror / Atom feed
From: "Dipl.-Ing. Michael Niederle" <mniederle-RbZlAiThDcE@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: Some problems
Date: Sat, 23 May 2009 22:11:20 +0200	[thread overview]
Message-ID: <20090523221120.086a1002@simplux> (raw)
In-Reply-To: <mailman.1.1243047601.4877.users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org>

Hi!

I continue testing nilfs as a root file system. Until now I have no script to
cleanly unmount the root file system. (In the layered approach (aufs) I used
before this was not necessary.) So I just called sync and then shut down the
system.

The next boot took some time, because the superblock was "broken". Here an
extract from the kernel log:

[    1.407323] NILFS warning: broken superblock. using spare superblock.
[    1.408569] NILFS warning: broken superblock. using spare superblock.
[  461.587031] segctord starting. Construction interval = 5 seconds, CP
frequency < 30 seconds [  461.591873] NILFS warning: mounting unchecked fs
[  461.629865] NILFS: recovery complete.

Is nilfs doing a sequential scan over the whole partition to find its spare
superblock?

Then I wanted to remove some snapshots:

> lscp -s
                 CNO        DATE     TIME  MODE  FLG   NBLKINC       ICNT
                 685  2009-05-13 09:38:20   ss    -         35     568722
                1330  2009-05-13 10:59:41   ss    i       7629     579584
                4466  2009-05-14 19:15:28   ss    -         23     589270
                8250  2009-05-16 03:40:42   ss    i       6202     597141
                9910  2009-05-17 19:14:54   ss    -         49     626715
               10380  2009-05-17 20:21:53   ss    -         18     647228
               10620  2009-05-23 21:45:41   ss    i       6054     646978

>rmcp 685
rmcp: 685: operation not permitted

What's the cause of this message? (rmcp also failed for all other snapshots;
the failed rmcp did not produce any kernel message)

Greetings, Michael

       reply	other threads:[~2009-05-23 20:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1243047601.4877.users@nilfs.org>
     [not found] ` <mailman.1.1243047601.4877.users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org>
2009-05-23 20:11   ` Dipl.-Ing. Michael Niederle [this message]
2009-05-24  8:51     ` Some problems Ryusuke Konishi
     [not found]       ` <20090524.175101.94865345.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-05-25 21:39         ` 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=20090523221120.086a1002@simplux \
    --to=mniederle-rbzlaithdce@public.gmane.org \
    --cc=users-JrjvKiOkagjYtjvyW6yDsg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox