From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: csaba.kos-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: Re: Can't mount nilfs - error searching super root.
Date: Fri, 16 Jan 2009 22:22:55 +0900 (JST) [thread overview]
Message-ID: <20090116.222255.131926946.ryusuke@osrg.net> (raw)
In-Reply-To: <55b53420901160316h2b1e70e3xc420321973ce99b4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Fri, 16 Jan 2009 20:16:55 +0900, "Csaba Kos" wrote:
> On Fri, Jan 16, 2009 at 8:07 PM, Ryusuke Konishi wrote:
> > On Fri, 16 Jan 2009 19:22:46 +0900, "Csaba Kos" wrote:
> >> Hi!
> >>
> >> Sorry to chime in uncalled, but I noticed that you are trying to mount
> >> "/dev/sdb".
> >> I have to admit that it has been a while since I last mounted a
> >> pendrive from the
> >> command line, so I might be wrong, but usually one mounts partitions
> >> on the device,
> >> like "/dev/sdb1", and not the device itself.
> >
> > No, no. That's OK.
> > NILFS does not overwrite the partition table block, so is available
> > for the device itself.
> > Of course, it's unless there's a bug for this usage ;)
> Ah, sorry, I didn't know about that and thank you for the heads up. So
> sdb and sdb1 is basically equivalent for nilfs?
No. If you did mkfs for sdb, the mount device must be sdb (not sdb1),
and the opposite is true. So they differ.
> Is this a nilfs-specific feature?
I believe most filesystems can do this.
One of the merits to use device itself is that it can align the
disk area without inserting offset sectors.
Since performance of flash devices is often sensitive to alignment of
sectors, this style is occasionally used.
Cheers,
Ryusuke
> Regards,
>
> Csaba
>
> >
> > Ryusuke
> >
> >> Regards,
> >>
> >> Csaba Kos
> >>
> >> On Fri, Jan 16, 2009 at 6:38 PM, Milos Jana <milosdsax-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> >> > user@laptop:~/prog/sources/nilfs-utils-2.0.6$ sudo fsck0.nilfs2 /dev/sdb
> >> > [sudo] password for user:
> >> > Super-block:
> >> > revision = 2.0, checksum = OK
> >> > blocksize = 4096
> >> > write time = 2008-12-28 09:48:42
> >> > indicated partial segment: blocknr = 4263936
> >> > segnum = 2082, seq = 11746, cno=6661
> >> >
> >> > empty or bad segment: segnum = 2082, blocknr = 4263936
> >> > The latest segment is lost. Trying rollback recovery..
> >> > .
> >> > Searching the latest checkpoint.
> >> > Selected segment: blocknr = 4261888
> >> > segnum = 2081, seq = 11745, cno=6660
> >> > creation time = 2008-12-28 09:48:34
> >> > Do you wish to overwrite super block (y/N)? Y
> >> > Recovery will complete on mount.
> >> > user@laptop:~/prog/sources/nilfs-utils-2.0.6$ sudo mount /media/pendrive/
> >> > mount.nilfs2: Error while mounting /dev/sdb on /media/pendrive: Invalid
> >> > argument
> >> >
> >> > dmesg returns the same errors:
> >> > [ 553.003240] NILFS warning: Segment magic number invalid
> >> > [ 553.003248] NILFS: error searching super root.
> >> >
> >> > On Fri, Jan 16, 2009 at 8:55 AM, Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org> wrote:
> >> >>
> >> >> On Thu, 15 Jan 2009 19:10:19 +0100, "Milos Jana" wrote:
> >> >> > Nilfs-utils compiled properly with patch after following instructions
> >> >> > from
> >> >> > your previous post. Here is what came out:
> >> >> >
> >> >> > user@laptop:~$ sudo fsck0.nilfs2 /dev/sdb
> >> >> > Super-block:
> >> >> > revision = 2.0, checksum = OK
> >> >> > blocksize = 4096
> >> >> > write time = 2008-12-28 09:48:42
> >> >> > indicated partial segment: blocknr = 4263936
> >> >> > segnum = 2082, seq = 11746, cno=6661
> >> >> >
> >> >> > Clean FS.
> >> >> >
> >> >> > user@laptop:~$ sudo mount /media/pendrive/
> >> >> > mount.nilfs2: Error while mounting /dev/sdb on /media/pendrive: Invalid
> >> >> > argument
> >> >>
> >> >> Hmm, that's weird.
> >> >>
> >> >> The partition was cleanly unmounted, but the final segment seems not
> >> >> to be written to the disk.
> >> >>
> >> >> Maybe, we need 'force' option to treat such situation.
> >> >>
> >> >> In the meatime, could you try the following (additional) patch?
> >> >>
> >> >> Regards,
> >> >> Ryusuke
> >> >> --
> >> >>
> >> >> diff --git a/sbin/mkfs/fsck0.nilfs2.c b/sbin/mkfs/fsck0.nilfs2.c
> >> >> index d3d335f..0d51e54 100644
> >> >> --- a/sbin/mkfs/fsck0.nilfs2.c
> >> >> +++ b/sbin/mkfs/fsck0.nilfs2.c
> >> >> @@ -905,10 +905,12 @@ static void nilfs_fsck(const char *device)
> >> >> print_pseg_message(&pseg_ref, " indicated partial segment");
> >> >> fputc('\n', stderr);
> >> >>
> >> >> +#if 0
> >> >> if (le16_to_cpu(sb.s_state) & NILFS_VALID_FS) {
> >> >> fprintf(stderr, "Clean FS.\n");
> >> >> goto out_clean;
> >> >> }
> >> >> +#endif
> >> >>
> >> >> if (nilfs_do_recovery(devfd, &pseg_ref) == 0)
> >> >> goto out;
> >> >
> >> >
> >> > _______________________________________________
> >> > users mailing list
> >> > users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
> >> > https://www.nilfs.org/mailman/listinfo/users
> >> >
> >> >
> >> _______________________________________________
> >> users mailing list
> >> users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
> >> https://www.nilfs.org/mailman/listinfo/users
> >
next prev parent reply other threads:[~2009-01-16 13:22 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 [this message]
[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
[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=20090116.222255.131926946.ryusuke@osrg.net \
--to=ryusuke-sg5x7nla6pw@public.gmane.org \
--cc=csaba.kos-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