Linux NILFS development
 help / color / mirror / Atom feed
From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: third07-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Response to a Write Error
Date: Fri, 16 Apr 2010 21:31:51 +0900 (JST)	[thread overview]
Message-ID: <20100416.213151.77349735.ryusuke@osrg.net> (raw)
In-Reply-To: <j2kf2d3ba1f1004141746n9f914465q3e24d48bec7f990e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hi
On Wed, 14 Apr 2010 20:46:46 -0400, "Ed F." <third07-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > The following are the steps to make&install a newer nilfs in the
> > 2.6.31 kernel.
> >
> >  $ sudo apt-get install linux-headers-`uname -r`
> >  $ cd /usr/src
> >  $ wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.32.11.tar.bz2
> >  $ tar jxf linux-2.6.32.11.tar.bz2
> >  $ cd linux-2.6.32.11/fs/nilfs2
> >  $ make -C /lib/modules/`uname -r`/build SUBDIRS=$PWD BUILD_DIR=$PWD modules
> >  $ su
> >  # rmmod nilfs2
> >  # mv /lib/modules/`uname -r`/kernel/fs/nilfs2/nilfs2.ko{,.bak}
> >  # install -m 644 -c nilfs2.ko /lib/modules/`uname -r`/kernel/fs/nilfs2/
> >  # /sbin/depmod -A
> >  # mount -t nilfs2 <device> <mount-dir>
> 
> Thank you for clarifying that process.  It will be very useful in
> keeping the kernel module up-to-date.

Please note that this procedure is not guaranteed.  This may not work
for some version since internal implementation or semantics of the
kernel often changes.

> If my analysis is correct, I have a DVD-RAM disk that has no more
> sectors with which my DVD drive can correct defects.  Would you like
> for me to save that disk for future error handling experiments?

Thanks for the offer.
I have interests in what happens on the latest kernel.
If you have an opportunity to try it, please report the result.

Ideally, it is expected to skip erroneous segments.
In reality, something unexpected may happen ;)

Cheers,
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-04-16 12:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-13 23:38 Response to a Write Error Ed F.
     [not found] ` <t2kf2d3ba1f1004131638nb61e68cek1ecb43a86c316d35-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-04-14 16:51   ` Ryusuke Konishi
     [not found]     ` <20100415.015106.58888665.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-04-15  0:46       ` Ed F.
     [not found]         ` <j2kf2d3ba1f1004141746n9f914465q3e24d48bec7f990e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-04-16 12:31           ` Ryusuke Konishi [this message]
     [not found]             ` <20100416.213151.77349735.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-04-20  8:39               ` Writes doubled by NILFS2 Yongkun Wang
2010-04-20 11:45                 ` Ryusuke Konishi
     [not found]                   ` <20100420.204523.76757028.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-04-21 14:41                     ` Yongkun Wang
2010-04-21 16:59                       ` Ryusuke Konishi
     [not found]                         ` <20100422.015907.119858125.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-04-22 13:54                           ` Yongkun Wang
2010-04-23 15:59                             ` Ryusuke Konishi
     [not found]                               ` <20100424.005941.176067504.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-04-25 14:10                                 ` Yongkun Wang
2010-04-25 16:12                                   ` 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=20100416.213151.77349735.ryusuke@osrg.net \
    --to=ryusuke-sg5x7nla6pw@public.gmane.org \
    --cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=third07-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