From: "Sachin Gaikwad" <sachin.kernel@gmail.com>
To: "Jim Cromie" <jim.cromie@gmail.com>,
"kernel learner" <kernellearner@gmail.com>,
linux-fsdevel@vger.kernel.org, kernelnewbies@nl.linux.org
Subject: Re: Upgrading datastructures between different filesystem versions
Date: Wed, 26 Sep 2007 18:29:19 -0500 [thread overview]
Message-ID: <f5524d840709261629t6268a050i7483d0229a57cd92@mail.gmail.com> (raw)
In-Reply-To: <20070926161756.GU32520@schatzie.adilger.int>
On 9/26/07, Andreas Dilger <adilger@clusterfs.com> wrote:
> On Sep 25, 2007 23:40 -0600, Jim Cromie wrote:
> > kernel learner wrote:
> > >ext3 filesystem has 32-bit block address and ext4 filesystem has
> > >48-bit block address. If a user installs ext4, how will the file
> > >system handle already existing block with 32 bit values?
> >
> > Why should it ? thats what ext3 is for.
>
> Bzzt. Wrong answer. The ext4 code will be able to read existing ext3
> (and ext2) filesystems just fine. Otherwise there wouldn't be much
> of an upgrade path.
>
> > Id expect ext4 drivers handling ext3 filesystems is a distant, secondary
> > goal to getting a fast, reliable, clean 48bit filesystem working.
>
> Far from the truth. One of the main goals of ext4 is that it is a drop-in
> replacement for ext3. The code is mostly incremental improvements over
> ext3, and that IS one of the reasons that it is reliable. We didn't throw
> away 10 years of bug fixes in the ext2/ext3 code when adding the ext4
> features.
>
> Cheers, Andreas
> --
> Andreas Dilger
> Principal Software Engineer
> Cluster File Systems, Inc.
>
>
> --
> To unsubscribe from this list: send an email with
> "unsubscribe kernelnewbies" to ecartis@nl.linux.org
> Please read the FAQ at http://kernelnewbies.org/FAQ
>
>
Is it not the case that VFS takes care of all filesystems available ?
VFS will see if a particular file belongs to ext3 or ext4 and call
that FS's drivers to access information ??
Correct me if I am wrong. I am a newbie!
Sachin
next prev parent reply other threads:[~2007-09-26 23:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 15:27 Upgrading datastructures between different filesystem versions kernel learner
2007-09-26 5:40 ` Jim Cromie
2007-09-26 16:17 ` Andreas Dilger
2007-09-26 23:29 ` Sachin Gaikwad [this message]
2007-09-27 0:53 ` Theodore Tso
2007-09-28 13:11 ` Erik Mouw
2007-09-28 13:31 ` Christoph Hellwig
2007-09-28 19:47 ` Theodore Tso
2007-09-29 9:05 ` Christoph Hellwig
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=f5524d840709261629t6268a050i7483d0229a57cd92@mail.gmail.com \
--to=sachin.kernel@gmail.com \
--cc=jim.cromie@gmail.com \
--cc=kernellearner@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).