From: Francis SOUYRI <francis.souyri@wanadoo.fr>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] which filesystem to use on slackware
Date: Mon Jan 12 14:08:02 2004 [thread overview]
Message-ID: <4002F072.90808@wanadoo.fr> (raw)
In-Reply-To: <20040112115400.GA29090@deepthought.hausboot.org>
Hi Jens,
Jens Hoffrichter wrote:
>On Sat, Jan 10, 2004 at 11:01:19AM +0100, Francis SOUYRI wrote:
>
>
>
>>With Ext3 you can grow the filesystem offline and with a kernel patch
>>you can grow online, you can not shrink.
>>
>>
>This is not true. Using resize2fs you can grow and shrink the filesystem,
>but only offline. I'm not sure about the kernel-patch, but I'm certainly
>sure you can shrink at least offline. And using e2fsadm in conjunction
>
>
Excuse me yes it is possible to shrink offline an ext2 filesystem.
For the online grow kernel patch there are informations at:
http://ext2resize.sourceforge.net/
or
http://sourceforge.net/projects/ext2resize/
For the merge of the patch in the 2.6 kernel there are informations at:
http://www.kernelnewbies.org/status/latest.html
or
http://kerneltrap.org/node/view/716
but I can not find the patch.
>with lvm is even more comfortable ;)) Although it had some issues with
>ext3, as sometimes a filesystem is reported unchecked even if you have run
>an e2fsck -f just right before. But adding a -f to resize2fs has always
>worked for me without any trouble at all.
>
>I chose ext3 2 1/2 years ago, when doing kernel development for my diploma
>thesis, and an occassional ooops or other crash happened almost regularily.
>And waiting for the filesystem check annoyed me after the 3rd time ;)
>
>The argument for ext3 at this moment was, that you can easily convert an
>ext2 filesystem to an ext3 filesystem using tune2fs -j (to add the journal),
>and even mount the ext3 filesystem as ext2, making it available even if
>you have no support for ext3 in your kernel (2 1/2 years ago quite important!)
>
>Ext3 has never failed me in this time, I had no failure of filesystem and
>the performance was also good, at least for my needs :)
>
>CU all,
>Jens
>
>
Best regards.
Francis
prev parent reply other threads:[~2004-01-12 14:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 19:02 [linux-lvm] which filesystem to use on slackware Chris Conn
2004-01-09 19:26 ` Greg Freemyer
2004-01-09 22:34 ` David Johnston
2004-01-10 5:02 ` Francis SOUYRI
2004-01-10 7:22 ` [linux-lvm] " Måns Rullgård
2004-01-10 11:36 ` Chris Conn
2004-01-10 12:29 ` Måns Rullgård
2004-01-10 16:15 ` David Johnston
2004-01-12 6:55 ` [linux-lvm] " Jens Hoffrichter
2004-01-12 14:08 ` Francis SOUYRI [this message]
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=4002F072.90808@wanadoo.fr \
--to=francis.souyri@wanadoo.fr \
--cc=linux-lvm@sistina.com \
/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