From: BUCHMULLER Norbert <norbi.lists@nix.hu>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] error on extending ext3
Date: Fri, 21 Oct 2005 17:57:21 +0200 [thread overview]
Message-ID: <20051021175721.2c84b738.norbi.lists@nix.hu> (raw)
In-Reply-To: <ED9BF0756A45484AB3EAB2E20D1AD49C7D9DC5@server4.bfc.net>
On Wed, 19 Oct 2005 01:10:10 +0200
"Durnin, Robert" <robert.durnin@bfc.net> wrote:
> itself to be the correct size. However, when I try to run resize2fs I
> get messages coming back which say it is impossible and even full.
Hello!
Can you please send us a copy of the messages (and the exact steps you
made)? (I think that the data you sent was lesser than anyone can help
you.)
norbi
next prev parent reply other threads:[~2005-10-21 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-18 23:10 [linux-lvm] error on extending ext3 Durnin, Robert
2005-10-19 17:22 ` Bill Ranck
2005-10-21 15:57 ` BUCHMULLER Norbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-22 9:03 Durnin, Robert
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=20051021175721.2c84b738.norbi.lists@nix.hu \
--to=norbi.lists@nix.hu \
--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).