Linux NILFS development
 help / color / mirror / Atom feed
From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org,
	yuri-EJC0RcYdacHR7s880joybQ@public.gmane.org
Subject: Re: Fail to mount NILFS.
Date: Sat, 22 Aug 2009 11:25:33 +0900 (JST)	[thread overview]
Message-ID: <20090822.112533.68801227.ryusuke@osrg.net> (raw)
In-Reply-To: <200908211918.34720.yuri-EJC0RcYdacHR7s880joybQ@public.gmane.org>

[-- Attachment #1: Type: Text/Plain, Size: 1341 bytes --]

Hi,
On Fri, 21 Aug 2009 19:18:34 +0300, Yuri Chislov wrote:
> Hi,
> 
>  I get error when mount nilfs2 partition.
> 
> mount.nilfs2 /dev/cciss/c0d1p1 /home/
> 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.
> mount.nilfs2: Error while mounting /dev/cciss/c0d1p1 on /home/: Invalid 
> argument
> 
> dmesg output:
> segctord starting. Construction interval = 5 seconds, CP frequency < 30 
> seconds
> NILFS: corrupt root inode.
> 
> Used kernel: 2.6.30.4
> nilfs-utils-2.0.12-3.i386
> 
> 
> Is it possible to fix the partition?
> Is it some tools exists, like fsck?
> 
> Thank you.
> Yuri.

Sorry for the inconvenience.
I'm afraid to say fsck has not been developed yet.

Are there any warnings or error messages of nilfs in syslog before the
problem ?

I'll attach a patch to allow nilfs to mount plain checkpoints.

If you made the kernel from source, try the patch as follows:

 $ cd linux-2.6.30.4
 $ patch -p1 < path-to/0001-nilfs2-remove-snapshot-check-on-mount.patch
 $ make modules
 $ sudo rmmod nilfs2
 $ sudo insmod fs/nilfs2/nilfs2.ko
 $ sudo mount -t nilfs2 -r -o cp=xxx /dev/yyy /mnt

If you succeed to mount a valid past checkpoint, you will be able to
do backup with rsync or so from the checkpoint.

Regards,
Ryusuke Konishi

[-- Attachment #2: 0001-nilfs2-remove-snapshot-check-on-mount.patch.bz2 --]
[-- Type: Application/Octet-Stream, Size: 951 bytes --]

[-- Attachment #3: Type: text/plain, Size: 158 bytes --]

_______________________________________________
users mailing list
users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
https://www.nilfs.org/mailman/listinfo/users

  parent reply	other threads:[~2009-08-22  2:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-21 16:18 Fail to mount NILFS Yuri Chislov
     [not found] ` <200908211918.34720.yuri-EJC0RcYdacHR7s880joybQ@public.gmane.org>
2009-08-22  2:25   ` Ryusuke Konishi [this message]
     [not found]     ` <20090822.112533.68801227.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-08-22  8:46       ` Yuri Chislov
     [not found]         ` <200908221146.28241.yuri-EJC0RcYdacHR7s880joybQ@public.gmane.org>
2009-08-22  9:50           ` Ryusuke Konishi
     [not found]             ` <20090822.185013.23110170.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-08-22 10:36               ` Yuri Chislov
     [not found]                 ` <200908221336.13326.yuri-EJC0RcYdacHR7s880joybQ@public.gmane.org>
2009-08-22 11:43                   ` Ryusuke Konishi
     [not found]                     ` <20090822.204316.57646960.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-08-22 12:34                       ` Ryusuke Konishi
     [not found]                         ` <20090822.213438.101583642.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-08-22 14:36                           ` Yuri Chislov
     [not found]                             ` <200908221736.42571.yuri-EJC0RcYdacHR7s880joybQ@public.gmane.org>
2009-08-22 16:21                               ` Ryusuke Konishi
     [not found]                                 ` <20090823.012139.108366726.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-08-22 16:36                                   ` Yuri Chislov
     [not found]                                     ` <200908221936.12308.yuri-EJC0RcYdacHR7s880joybQ@public.gmane.org>
2009-08-23  3:23                                       ` Ryusuke Konishi
     [not found]                                         ` <20090823.122322.09561031.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-08-23  4:55                                           ` Yuri Chislov
     [not found]                                             ` <200908230755.02831.yuri-EJC0RcYdacHR7s880joybQ@public.gmane.org>
2009-08-23  8:20                                               ` Ryusuke Konishi
  -- strict thread matches above, loose matches on Subject: below --
2009-08-23 13:06 Yuri Chislov
     [not found] ` <200908231606.17747.yuri-EJC0RcYdacHR7s880joybQ@public.gmane.org>
2009-08-23 13:09   ` Ryusuke Konishi
     [not found]     ` <20090823.220941.57456918.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-08-24 16:08       ` Ryusuke Konishi
     [not found]         ` <20090825.010847.29421896.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-08-24 16:21           ` Yuri Chislov
     [not found]             ` <200908241921.35124.yuri-EJC0RcYdacHR7s880joybQ@public.gmane.org>
2009-08-24 17:33               ` Ryusuke Konishi
     [not found]                 ` <20090825.023349.64850558.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-08-24 18:11                   ` Yuri Chislov

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=20090822.112533.68801227.ryusuke@osrg.net \
    --to=ryusuke-sg5x7nla6pw@public.gmane.org \
    --cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org \
    --cc=yuri-EJC0RcYdacHR7s880joybQ@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