From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: Ted Ts'o <tytso@mit.edu>
Cc: Lukas Czerner <lczerner@redhat.com>,
linux-ext4@vger.kernel.org, sandeen@redhat.com
Subject: Re: [PATCH 4/4] e2fsck: Add QCOW2 support
Date: Mon, 28 Feb 2011 10:44:44 +0100 [thread overview]
Message-ID: <20110228094444.GD4834@bitwizard.nl> (raw)
In-Reply-To: <20110226164442.GD2924@thunk.org>
On Sat, Feb 26, 2011 at 11:44:42AM -0500, Ted Ts'o wrote:
> ext2/3/4's 2TB maximum file size limit. The qcow2 image might be only
> a few hundreds of megabytes, so being able to have e2fsck operate on
> that image directly would be a huge win.
driepoot:~> ls -ls /mnt/md3.img
61558920 -rw------- 1 root root 2937535070208 Feb 26 00:36 /mnt/md3.img
61 Gigabytes in my case... (and my system finished counting: I have
8.9M directories on there...)
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement.
Does it sit on the couch all day? Is it unemployed? Please be specific!
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ
next prev parent reply other threads:[~2011-02-28 9:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 12:49 [PATCH 1/4] e2image: Add support for qcow2 format Lukas Czerner
2011-02-25 12:49 ` [PATCH 2/4] e2image: Support for conversion QCOW2 image into raw Lukas Czerner
2011-02-25 12:49 ` [PATCH 4/4] e2fsck: Add QCOW2 support Lukas Czerner
2011-02-26 16:44 ` Ted Ts'o
2011-02-28 9:44 ` Rogier Wolff [this message]
2011-03-01 11:42 ` Lukas Czerner
2011-03-07 10:40 ` Amir Goldstein
2011-03-07 12:40 ` Lukas Czerner
2011-03-09 16:30 ` Lukas Czerner
2011-03-09 17:52 ` Amir Goldstein
2011-03-17 13:05 ` Lukas Czerner
2011-02-26 16:28 ` [PATCH 1/4] e2image: Add support for qcow2 format Ted Ts'o
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=20110228094444.GD4834@bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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).