From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: milosdsax-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: Re: Can't mount nilfs - error searching super root.
Date: Thu, 12 Feb 2009 14:34:08 +0900 (JST) [thread overview]
Message-ID: <20090212.143408.130857730.ryusuke@osrg.net> (raw)
In-Reply-To: <3313c4ab0902110709v1e9783fcm8f3dad6507f40347-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi,
On Wed, 11 Feb 2009 16:09:32 +0100, Milos Jana wrote:
> Uhm... does it mean that data from my pendrive in unrecoverable? Is there
> any chance that future release on fsck0.nilfs will be able to recover it?
> On Fri, Jan 30, 2009 at 1:03 PM, Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org> wrote:
Oh, sorry. I once looked into the fsck0, but it was paused because I
had to do so many things. I'll increase priority for this if you
really need it. Meanwhile I'm worrying that the same trouble occurs
again and again even if fsck0 will be improved.
I feel we think removing the cause of the problem because
making better fsck will take some time.
And I wonder why the pendrive does not write all data for cleanly
unmounted partition so often. It may need bugfix for the device driver,
for example it may have a silent error problem (i.e. it may complete
I/O operations even if it couldn't handle them properly).
Anyway, I will be able to back to fsck0 after a while.
Regards,
Ryusuke
> > Hi,
> > On Sat, 24 Jan 2009 01:13:41 +0100, Milos Jana wrote:
> > > Hi again,
> > >
> > > Looks like I'm unable to mount this drive again. It mounted successfully
> > > several times after following your previous posts, but yesterday the
> > problem
> > > came back. I'm sure that I have been mounting/unmounting my pendrive
> > > properly.
> >
> > Hmm, it's abnormal that this occurs so often.
> > The partition was cleanly unmounted, but the latest segment was not
> > written.
> > The usb device seems to lack proper support of cache flushing if it
> > occurs just before power-off.
> >
> > The usb stack of Linux is often problematic, but this looks terrific.
> >
> > > This time fsck0.nilfs2 doesn't help - it hangs with "Searching the
> > > latest checkpoint." message (see below).
> >
> > All right, I'll look into the hang problem.
> >
> > Please note that the fsck0 is not a complete solution.
> > To make it better, we need a few changes on the disk format.
> >
> > Regards,
> > Ryusuke
> >
> > > user@laptop:~$ sudo mount /media/pendrive/
> > > mount.nilfs2: Error while mounting /dev/sdb on /media/pendrive: Invalid
> > > argument
> > >
> > > user@laptop:~$ dmesg
> > > ...
> > > [22429.446924] NILFS warning: Segment magic number invalid
> > > [22429.446932] NILFS: error searching super root.
> > >
> > > user@laptop:~/prog/sources/nilfs-utils-2.0.6$ sudo fsck0.nilfs2 /dev/sdb
> > #
> > > Nilfs-tools with first patch applied
> > > Super-block:
> > > revision = 2.0, checksum = OK
> > > blocksize = 4096
> > > write time = 2009-01-22 23:40:19
> > > indicated partial segment: blocknr = 1966080
> > > segnum = 960, seq = 18266, cno=10169
> > >
> > > Clean FS.
> > >
> > > user@laptop:~/prog/sources/nilfs-utils-2.0.6$ sudo fsck0.nilfs2 /dev/sdb
> > #
> > > Nilfs-tools with additional patch applied
> > > Super-block:
> > > revision = 2.0, checksum = OK
> > > blocksize = 4096
> > > write time = 2009-01-22 23:40:19
> > > indicated partial segment: blocknr = 1966080
> > > segnum = 960, seq = 18266, cno=10169
> > >
> > > empty or bad segment: segnum = 960, blocknr = 1966080
> > > The latest segment is lost. Trying rollback recovery..
> > > .
> > > Searching the latest checkpoint. # here it hanged for like 10 minutes
> > > until I killed it
> >
next prev parent reply other threads:[~2009-02-12 5:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 15:03 Can't mount nilfs - error searching super root Milos Jana
[not found] ` <3313c4ab0901150703o5f86dc67y9261156a5519e1d5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-01-15 17:01 ` Ryusuke Konishi
[not found] ` <20090116.020115.07539201.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-01-15 18:10 ` Milos Jana
[not found] ` <3313c4ab0901151010u67983034vd1b8b75e0672d400-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-01-16 7:55 ` Ryusuke Konishi
[not found] ` <20090116.165503.64733535.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-01-16 9:38 ` Milos Jana
[not found] ` <3313c4ab0901160138u39baa485u56c5f285fb553449-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-01-16 10:02 ` Ryusuke Konishi
[not found] ` <20090116.190200.71915952.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-01-16 11:15 ` Milos Jana
2009-01-16 10:22 ` Csaba Kos
[not found] ` <55b53420901160222g3716f81cy229069f7af717283-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-01-16 11:07 ` Ryusuke Konishi
[not found] ` <20090116.200749.101561788.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-01-16 11:16 ` Csaba Kos
[not found] ` <55b53420901160316h2b1e70e3xc420321973ce99b4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-01-16 13:22 ` Ryusuke Konishi
[not found] ` <20090116.222255.131926946.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-01-24 0:13 ` Milos Jana
[not found] ` <3313c4ab0901231613g2d82ea3at13e524dfba28df4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-01-24 0:22 ` Milos Jana
2009-01-30 12:03 ` Ryusuke Konishi
[not found] ` <20090130.210323.88475416.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-02-11 15:09 ` Milos Jana
[not found] ` <3313c4ab0902110709v1e9783fcm8f3dad6507f40347-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-02-12 5:34 ` Ryusuke Konishi [this message]
[not found] ` <20090212.143408.130857730.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-04-22 13:18 ` Milos Jana
[not found] ` <3313c4ab0904220618r22b62e7qa8b239ccbcf02270-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-04-22 14:44 ` Ryusuke Konishi
[not found] ` <20090422.234455.05227091.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-05-10 14:50 ` Milos Jana
[not found] ` <3313c4ab0905100750p503664acl3b44d043db3d23ae-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-05-11 15:32 ` Milos Jana
[not found] ` <3313c4ab0905110832r6ca78e18h570a6f89d6078be6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-05-11 18:52 ` Ryusuke Konishi
2009-02-11 15:20 ` Milos Jana
-- strict thread matches above, loose matches on Subject: below --
2009-01-14 22:04 Milos Jana
[not found] ` <3313c4ab0901141404h97995dgf58282876b0ffd42-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-01-15 11:48 ` 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=20090212.143408.130857730.ryusuke@osrg.net \
--to=ryusuke-sg5x7nla6pw@public.gmane.org \
--cc=milosdsax-Re5JQEeQqe8AvxtiuMwx3w@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