From: Mag Gam <magawake@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
Marc-Jano Knopp <pub_ml_lvm@marc-jano.de>
Subject: Re: [linux-lvm] LVM onFly features
Date: Sat, 10 Dec 2005 22:38:46 -0500 [thread overview]
Message-ID: <1cbd6f830512101938g4ec7d36dq4fd9a081658edf47@mail.gmail.com> (raw)
In-Reply-To: <20051210230341.GJ3103@mjk.myfqdn.de>
thanks everyone for their kind replies.
So, will LVM and FS (ext2/3 in particular )ever be considered as 1?
This would be nice for ease of devt.
On 12/10/05, Marc-Jano Knopp <pub_ml_lvm@marc-jano.de> wrote:
> On Sat, 10 Dec 2005 at 15:51 (-0700), Michael Loftis wrote:
> > --On December 10, 2005 3:44:00 PM -0700 Michael Loftis <mloftis@wgops.com>
> > wrote:
> > >--On December 10, 2005 11:31:40 PM +0100 Marc-Jano Knopp <pub_ml_lvm@marc-jano.de> wrote:
> [...]
> > >Any tail can be packed if it doesn't match the block size. In our case
> > >the corruption evidenced itself as files with the first part being ok,
> > >and the last part being all NULLs (0x0) up to the 'normal' file size.
> >
> > I really should say *mostly* because yes, files that were entirely shorter
> > than the blocksize were essentially gone (full of NULLs).
>
> I knew it. :-)
>
>
> > Our mail server makes the best use of reiserfs because of the huge number
> > of files and the amount of files that end up packed.
>
> Same effect with news spool here (until ReiserFS lost files and I
> returned remorsefully to ext3 :-).
>
>
> Best regards
>
> Marc-Jano
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
next prev parent reply other threads:[~2005-12-11 3:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-10 19:38 [linux-lvm] LVM onFly features Mag Gam
2005-12-10 19:48 ` Marc-Jano Knopp
2005-12-10 20:03 ` Michael Loftis
2005-12-10 20:06 ` Marc-Jano Knopp
2005-12-10 20:14 ` Michael Loftis
2005-12-10 20:22 ` Marc-Jano Knopp
2005-12-10 22:10 ` Michael Loftis
2005-12-10 22:31 ` Marc-Jano Knopp
2005-12-10 22:44 ` Michael Loftis
2005-12-10 22:51 ` Michael Loftis
2005-12-10 23:03 ` Marc-Jano Knopp
2005-12-11 3:38 ` Mag Gam [this message]
2005-12-11 7:43 ` Michael Loftis
2005-12-11 14:08 ` Fredrik Tolf
2005-12-11 15:32 ` Mag Gam
2005-12-15 20:44 ` David Johnston
2005-12-18 0:27 ` Mag Gam
2005-12-11 22:15 ` Nathan Scott
2005-12-12 1:14 ` Michael Loftis
2005-12-12 2:28 ` Nathan Scott
2005-12-10 20:47 ` Graham Wood
2005-12-13 16:56 ` Stephen C. Tweedie
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=1cbd6f830512101938g4ec7d36dq4fd9a081658edf47@mail.gmail.com \
--to=magawake@gmail.com \
--cc=linux-lvm@redhat.com \
--cc=pub_ml_lvm@marc-jano.de \
/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).