On Wed, Apr 2, 2008 at 2:13 AM, Alan McKinnon <[EMAIL PROTECTED]> wrote:
> On Tuesday 01 April 2008, fei huang wrote: > > thank you for the reply, actually I've heard about this solution, and > > tried to use resize2fs to expand my filesystem (ext3), the problem is > > I didn't know how to use it, what does the "new size" parameter mean? > > the additional size or the new complete size? and the device must be > > a partition rather than the whole disk, otherwise, it complains "Bad > > magic number in super-block", and for a partition, it complains size > > not match or too large. any ideas? > > You have to resize the "thing" on which the filesystem resides. In other > words, this is the first parameter you would supply when mounting it. > If your filesystem is a whole disk, then you resize the disk. If it's a > partition, then supply the partition device node as parameter. Similar > with LVM volumes, raid volumes or whatever other gadget your filesystem > is on. > > resize2fs is quite smart, if you don't supply a size, it expands the > filesystem to take up the entire device. Let's say the filesystem is > on /dev/sda3, you would then just do: > > resize2fs /dev/sda3 > > Don't worry about unmounting the device or anything like that, growing a > filesystem can be done live and on-line > I think this probably only works in the case that the raw free space is phyically located beside the specified partition, imagine there are sda1, sda2 in sequence, when new space available, resize only possible to sda2, and with a disk with 4 primary partitions, this won't help either.. am I right? ~ resize didn't work for me, I backup my data, and recreated the partition with a new size, old way but make more sense to me. thanks so much, I'll try it later in another VM in my office. regards fei > -- > Alan McKinnon > alan dot mckinnon at gmail dot com > > -- > gentoo-user@lists.gentoo.org mailing list > >
