Linux NILFS development
 help / color / mirror / Atom feed
From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: rdeleonp-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Error while testing (using loop device)
Date: Fri, 23 Jul 2010 11:31:25 +0900 (JST)	[thread overview]
Message-ID: <20100723.113125.163336402.ryusuke@osrg.net> (raw)
In-Reply-To: <AANLkTin0qMJvDgs705a9Nu0hWNLCdGEXWn7q_2sXQ6yZ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hi,
On Thu, 22 Jul 2010 14:26:38 -0500, Rodrigo_E._De_León_Plicet wrote:
> Hi.
> 
> Ubuntu 10.04
> nilfs-tools 2.0.15
> 
> --------------------------------------------------------------------------------
> 
> rdl@linage:/tmp$ mkdir t
> 
> rdl@linage:/tmp$ mkdir t2
> 
> rdl@linage:/tmp$ chmod 777 t t2
> 
> rdl@linage:/tmp$ dd if=/dev/zero of=test.img bs=1M seek=1000 count=1
> 1+0 records in
> 1+0 records out
> 1048576 bytes (1.0 MB) copied, 0.00422859 s, 248 MB/s
> 
> rdl@linage:/tmp$ mkfs -t nilfs2 test.img
> mkfs.nilfs2 ver 2.0
> Start writing file system initial data to the device
>       Blocksize:4096  Device:test.img  Device Size:1049624576
> File system initialization succeeded !!
> 
> rdl@linage:/tmp$ sudo mount -t nilfs2 -o loop /tmp/test.img /tmp/t
> mount.nilfs2: WARNING! - The NILFS on-disk format may change at any time.
> mount.nilfs2: WARNING! - Do not place critical data on a NILFS filesystem.
> 
> (... time passes ...)
> 
> rdl@linage:/tmp$ lscp
>                 CNO        DATE     TIME  MODE  FLG   NBLKINC       ICNT
>                   1  2010-07-21 15:25:07   cp    -         11          3
>                   2  2010-07-21 15:26:47   cp    -        118          4
>                   3  2010-07-21 15:26:56   cp    -        224          6
>                   4  2010-07-21 15:27:03   cp    -         23         12
>                   5  2010-07-21 15:27:14   cp    -         48         13
> 
> rdl@linage:/tmp$ sudo chcp ss 3
> 
> rdl@linage:/tmp$ lscp
>                 CNO        DATE     TIME  MODE  FLG   NBLKINC       ICNT
>                   1  2010-07-21 15:25:07   cp    -         11          3
>                   2  2010-07-21 15:26:47   cp    -        118          4
>                   3  2010-07-21 15:26:56   ss    -        224          6
>                   4  2010-07-21 15:27:03   cp    -         23         12
>                   5  2010-07-21 15:27:14   cp    -         48         13
>                   6  2010-07-21 15:27:33   cp    -         14         14
> 
> rdl@linage:/tmp$ sudo mount -t nilfs2 -o ro,cp=2,loop /tmp/test.img /tmp/t2
> mount.nilfs2: Error while mounting /dev/loop1 on /tmp/t2: Read-only file system
> 
> rdl@linage:/tmp$ sudo mount -t nilfs2 -r -o cp=2,loop /tmp/test.img /tmp/t2
> mount.nilfs2: Error while mounting /dev/loop1 on /tmp/t2: Read-only file system

How about this?

 $ sudo mount -t nilfs2 -o ro,cp=3,loop=/dev/loop0 /tmp/test.img /tmp/t2

or

 $ sudo mount -t nilfs2 -r -o cp=3,loop=/dev/loop0 /tmp/test.img /tmp/t2
 ...
 $ sudo umount /tmp/t2

Note that you have to manually detach the device like "losetup -d
/dev/loop0" if you once failed to mount it.  This is because the loop
device is handled by the common "mount" program not by "mount.nilfs2".

Regards,
Ryusuke Konishi
--
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:[~2010-07-23  2:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTikwTRGooDQD+Uo08MkywS+KJ8BXxqqytxbNFiqr@mail.gmail.com>
     [not found] ` <AANLkTikwTRGooDQD+Uo08MkywS+KJ8BXxqqytxbNFiqr-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-22 19:26   ` Error while testing (using loop device) Rodrigo E. De León Plicet
     [not found]     ` <AANLkTin0qMJvDgs705a9Nu0hWNLCdGEXWn7q_2sXQ6yZ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-23  2:31       ` Ryusuke Konishi [this message]
     [not found]         ` <20100723.113125.163336402.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-07-23 15:47           ` Rodrigo E. De León Plicet
     [not found]             ` <AANLkTikY4joAzVe-3BSpX9KNSmFPr8cXqpJ_0pJ+rX0P-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-23 16:31               ` 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=20100723.113125.163336402.ryusuke@osrg.net \
    --to=ryusuke-sg5x7nla6pw@public.gmane.org \
    --cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=rdeleonp-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