From: Oleg Drokin <green@namesys.com>
To: Chris Worley <chrisw@lnxi.com>
Cc: reiserfs-list@namesys.com
Subject: Re: 2GB limit won't go away
Date: Sun, 9 Jun 2002 23:16:08 +0400 [thread overview]
Message-ID: <20020609231608.B8386@namesys.com> (raw)
In-Reply-To: <1023754229.4654.1831.camel@xserver>
Hello!
The easiest way for you to go is to boot of rescue CD/diskette
and then mount your root as -o conv
(btw, SuSE 7.3 does not come with reiserfsprogs-3.x.0j-1)
Or if you do not use initrd during your normal boot, you can
issue 'lilo -R "linux rootfsflags=conv"' command and reboot.
replace linux with your usual lilo target if needed.
Flags that are passed from /etc/fstab are only applied to rootfs on
remount and you cannot convert fs on remount.
Bye,
Oleg
On Mon, Jun 10, 2002 at 06:10:28PM -0600, Chris Worley wrote:
> It's new files I'm trying to create. Am I missing something... such as
> LVM underneath is screwing something up? I just want to add to my
> existing partition, and not create new partitions.
>
> Thanks,
>
> Chris
>
> On Sun, 2002-06-09 at 12:35, Andreas Dilger wrote:
> > On Jun 10, 2002 05:28 -0600, Chris Worley wrote:
> > > I'm Running Linux 2.4.10-4GB on SuSE 7.3 with reiserfsprogs-3.x.0j-1
> > > (using 3.5.x disk format...ReiserFS version 3.6.25) atop
> > ^^^^^^^^^^^^^^^^^^^^^^^
> >
> > It is my understanding that you cannot use >2GB files with 3.5 disk
> > format. The only way to "upgrade" is to backup restore. If you
> > mount with the "conv" mount option, you apparently will be able to
> > create _new_ files in the 3.6 format (i.e. they can be > 2GB), but
> > existing files cannot grow past 2GB.
> >
> > You could "solve" this problem by doing something like:
> >
> > tar cf - /home | tar xf - -C /tmp
> > rm -r /home/*
> > mv /tmp/home/* /home/*
> > rmdir /tmp/home
> >
> > Which will re-create all of your files with the 3.6 format "inodes"
> > and get rid of your old format inodes. You have to be careful if
> > you do this, because you run the risk of accidentally deleting all
> > of your files if you do the wrong thing. If you have enough free
> > space in another partition, you may as well just format it with
> > 3.6 format and copy everything over and delete the old partition.
> >
> > Cheers, Andreas
> > --
> > Andreas Dilger
> > http://www-mddsp.enel.ucalgary.ca/People/adilger/
> > http://sourceforge.net/projects/ext2resize/
> >
>
>
next prev parent reply other threads:[~2002-06-09 19:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-09 6:13 2GB limit won't go away Chris Worley
[not found] ` <3D033CC6.70707@neuronet.pitt.edu>
2002-06-09 15:13 ` Chris Worley
2002-06-09 16:08 ` Valdis.Kletnieks
2002-06-09 18:52 ` Chris Worley
2002-06-09 18:35 ` Andreas Dilger
2002-06-09 18:55 ` Chris Worley
2002-06-09 19:16 ` Oleg Drokin [this message]
2002-06-10 2:11 ` Chris Worley
2002-06-10 4:58 ` Oleg Drokin
2002-06-10 5:42 ` Andreas Dilger
2002-06-10 14:00 ` Chris Worley
2002-06-10 14:05 ` Chris Worley
2002-06-10 14:09 ` Chris Worley
2002-06-10 16:08 ` Andreas Dilger
2002-06-10 15:47 ` Oleg Drokin
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=20020609231608.B8386@namesys.com \
--to=green@namesys.com \
--cc=chrisw@lnxi.com \
--cc=reiserfs-list@namesys.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.