All of lore.kernel.org
 help / color / mirror / Atom feed
From: "James B. Byrne " <ByrneJB@Harte-Lyne.ca>
To: linux-lvm@sistina.com
Subject: [linux-lvm] Re: linux-lvm digest, Vol 1 #624 - 8 msgs
Date: Thu Jul  4 10:12:02 2002	[thread overview]
Message-ID: <3D242D75.3370.4A25E76@localhost> (raw)
In-Reply-To: <E17Q3FS-0002v2-00@hermes.sistina.com>

On 4 Jul 2002 at 4:49, "Heinz J . Mauelshagen" 
<mauelshagen@sistina.com> wrote:

> Did you just grow the LV?
> 

Yes

> You need to extend the FS using the respective FS resizing tool as
> well (resize2fs, resize_reiserfs, ...).
> 

Did that too.

> BTW: for ext2 the e2fsadm(8) command, which comes with LVM does both
> for you.
> 
> 

I tried this originally but I can't remember if it worked first off or if in 
my ignorance I ran it out of sequence, had problems, and ended up 
doing something else.  In any case eventually I managed to get the 
file system up to 350 Mb.

> This doesn't really explain the local/remote difference unless:
> 
> - local users had root credentials avoiding the fs
>   "reserved block count" to matter

As it turned out the local user did have root capability but when su to 
a non-privileged user the local file transfers also worked.
> 
> - files uploaded where very large compared to the locally stored files

The reverse in fact, the local files moved in for testing averaged 10x 
the size of normal ftp uploads.  However, the culprit was discovered 
and it wasn't lvm.  The problem appears to have been a simple 
permission problem in the directory tree for the ftp chroot.  Why 
pureftpd chose to report this as a disk full error is beyond me.

However, it is worth noting that rebooting the system, without 
making any other changes, caused pureftp to subsequently report a 
different error message for the same activity. The message didn't 
actually say access forbidden ( I think that it was more like "non 
existent file", but with the application of a little intuition it did point to 
a permissions problem.  

Regards,
Jim


---     e-mail is NOT a secure channel 
James B. Byrne                mailto:ByrneJB@Harte-Lyne.ca
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3

       reply	other threads:[~2002-07-04 10:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E17Q3FS-0002v2-00@hermes.sistina.com>
2002-07-04 10:12 ` James B. Byrne  [this message]
2002-07-05  5:02   ` [linux-lvm] Re: linux-lvm digest, Vol 1 #624 - 8 msgs Heinz J . Mauelshagen

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=3D242D75.3370.4A25E76@localhost \
    --to=byrnejb@harte-lyne.ca \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.