Linux NILFS development
 help / color / mirror / Atom feed
From: Ryusuke Konishi <konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
To: zavi05-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Initial mount fails
Date: Sun, 04 Dec 2011 22:29:08 +0900 (JST)	[thread overview]
Message-ID: <20111204.222908.193237875.ryusuke@osrg.net> (raw)
In-Reply-To: <CAN67vW1TR8g=LBH6p+G4yj8UL9wCmjLghGJJOB3zzQjD-tC-Ug-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hi,
On Sun, 4 Dec 2011 11:10:12 +0200, Zavi wrote:
> Hi all,
> 
> I'm trying yo mount nilfs on a device without success.
> mkfs works just fine, but when I try to mount I keep getting an error
> > sudo mkfs -t nilfs2 /dev/sdc
> > sudo mount -t nilfs2 /dev/sdc ~/nilfs
> mount.nilfs2: Error while mounting /dev/sdc on ~/nilfs: Invalid argument
> 

Were there any related messages in logs?  Please try dmesg command or
make sure system logs:

 $ dmesg

 or 

 $ sudo cat /var/log/{messages,syslog}

Regards,
Ryusuke Konishi

> I've installed nilfs-utils, and this is what I get from fsck
> > sudo fsck0.nilfs2 -f -v /dev/sdc
> fsck0.nilfs2: cannot read super block (device=/dev/sdc)
> 
> just to be sure the problem is not in the device, I mounted ext4 on it
> successfuly.
> I can also do block requests (dd, iometer) without a problem.
> 
> I'd appreciate any suggestion.
> 
> Thanks,
> Zavi
> --
> 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
--
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

  parent reply	other threads:[~2011-12-04 13:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-04  9:10 Initial mount fails Zavi
     [not found] ` <CAN67vW1TR8g=LBH6p+G4yj8UL9wCmjLghGJJOB3zzQjD-tC-Ug-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-12-04 13:29   ` Ryusuke Konishi [this message]
     [not found]     ` <20111204.222908.193237875.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-12-04 16:38       ` Zavi
     [not found]         ` <CAN67vW2nSDWfESF1o2umuqduJY-MKL1da0oboDy04tyT4FEL5g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-12-04 17:13           ` Ryusuke Konishi
     [not found]             ` <20111205.021311.06955058.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-12-04 18:01               ` Zavi
     [not found]                 ` <CAN67vW2C3d5Byinib97otyCk9rujPhLSOmLXkC01juHo6e=nVA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-12-05  4:23                   ` Ryusuke Konishi
     [not found]                     ` <20111205.132326.69345131.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-12-05  8:56                       ` Zavi

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=20111204.222908.193237875.ryusuke@osrg.net \
    --to=konishi.ryusuke-zyj7fxus5i5l9jvzuh4aog@public.gmane.org \
    --cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=zavi05-Re5JQEeQqe8AvxtiuMwx3w@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