From: Gabriel Barazer <gabriel@oxeva.fr>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] very slow fw performance when snapshots active
Date: Thu, 18 Oct 2007 15:52:36 +0200 [thread overview]
Message-ID: <47176524.2080508@oxeva.fr> (raw)
In-Reply-To: <47171BD6.3090709@idmedia.com>
Hi,
On 10/18/2007 10:39:50 AM +0200, Falko Zurell <falko.zurell@idmedia.com>
wrote:
>
> Then I edit a 2 GB text file on /opt (XFS filesystem) with vi (just
> hitting "enter" and save this minor change). This will take minutes to
> finish the vi during saving.
This problem is not lvm-related: when opening a file with vim, it reads
the entire file into memory (even if the file is 2GB), marks the changes
into a .swp file. When saving, vim rewrites the entire file in place,
effectively changing 2GB of copy on write blocks. This happens every
time, with or without snapshot, the latter being worse because of the
cow overhead.
for reading-only very large files, "less" or "more" read files on-demand
which is a far more effecient way.
for writing, I don't know any method allowing to safely write a small
change into a large file, except using awk or perl parsing (which reads
the entire streamed file anyway)
Gabriel
next prev parent reply other threads:[~2007-10-18 13:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 8:39 [linux-lvm] very slow fw performance when snapshots active Falko Zurell
2007-10-18 13:52 ` Gabriel Barazer [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-18 14:01 AW: " Zurell, Falko
2007-10-18 15:18 ` Gabriel Barazer
2007-10-18 16:01 ` malahal
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=47176524.2080508@oxeva.fr \
--to=gabriel@oxeva.fr \
--cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).