10.04 install "quick format"

[fveggerby]

New install 10.04.1 on 1.3 TB HD

Problem is, that it formats the partitions full format.
This takes a VERY long time.

Is there any way I can avoid this?

I tried fiddling with the partition settings, but can't find anything.
Also tried making a manual partitioning, still no luck.
Only making "/" (ext4) and "swap"

Also I'm installing as a VmWare machine, with a growable disk. (Thin Provisioning)
That is kinda stupid, when it makes a full format. :)

[CharlesA]

Desktop or server?

I don't recall any way to make it do a "quick" format during install.

[Rubi1200]

I would recommend first preparing the drive using GParted from the LiveCD; that way when it comes time to install everything is ready.

But either way, as CharlesA pointed out, I don't think there is a "quick" way to do this.

[CharlesA]

I would recommend first preparing the drive using GParted from the LiveCD; that way when it comes time to install everything is ready.

That would work.

You'd have to do manual partitioning for Ubuntu Desktop and set it to not format that one.

You can do the same with the server install as well.

[fveggerby]

It is Server version.

Will (have) to try the LiveCD.
Is there 1 for the Server?

I do not have the option not to format.
(due to fresh install?)

[CharlesA]

A livecd is a livecd. You'd have to create the partiton first. :)

[fveggerby]

:confused:

I can't find any download for LiveCD.

Just use Desktop CD??

[Rubi1200]

:confused:

I can't find any download for LiveCD.

Just use Desktop CD??
http://releases.ubuntu.com/lucid/
The Desktop CD is the LiveCD.

[psusi]

Adding partman-ext3/lazy_itable_init=true to the boot parameters should do the trick.

[fveggerby]

LiveCD install:
Nope, same problem.
"Format" is greyed out.
](*,)

Is it really nessecary to install ex. 9.10 and then upgrade?
Is upgrading a good solution anyway?

[fveggerby]

Adding partman-ext3/lazy_itable_init=true to the boot parameters should do the trick.

I'm not the fastest LinuxShark on the planet.
But wouldn't that give me an ext3 partition, and not ext4?

And how is it, that I be able to give that parameter?

[fveggerby]

I'm not the fastest LinuxShark on the planet.
But wouldn't that give me an ext3 partition, and not ext4?

And how is it, that I be able to give that parameter?


Either it didn't work or I added the parameter wrong.
Pressed F6 for other options.
Added the parameter after "file=xxxxxxxxxx --"

Install Server 9.10, same problem.
Not possible to avoid formatting.

[psusi]

No, there is no avoiding the formatting; you can't put files on an unformatted partition. What that option will do is make sure that formatting goes much faster.

As an alternative, you can create the partition manually then format it with mke2fs -t ext4 -E lazy_itable_init=1.

[fveggerby]

hrmpf!

I don't understand why the quick format is not an option.
I'm very positive that in older versions it was possible. (and standard)

My problem is not that much the time issue, but that when using VmWare growable disks, (Thin Provisioning) all space is consumed, making Thin Provisioning unusable.

It is an issue with backup and moving VM guests.

Foolish that I have to work with a 1.3 TB file, when ther's only ex. 350 GB data in it.

When installing a *******, Thin Provisioning works as intended.

I will now test 8.04 Hardy LTS, just to be sure.

[fveggerby]

8.04 Hardy, same issue. :(

Problem must be elsewhere.
We have multible 8.04 running on VmWare Server 1, no problem.
But ESXi 4.0 U1 seems to have problems.

[psusi]

hrmpf!

I don't understand why the quick format is not an option.
I'm very positive that in older versions it was possible. (and standard)

Nope, it's a new feature that is still not fully implemented and thus, unsafe, which is why it is off by default.



My problem is not that much the time issue, but that when using VmWare growable disks, (Thin Provisioning) all space is consumed, making Thin Provisioning unusable.

Yep, that is exactly what lazy_itable_init is for. The problem is that if you aren't using a new completely blank disk, if you eventually have to run a fsck it can find old inodes from a previous fs that did not get zeroed out when you formatted and it will get VERY confused and muck up your filesystem.

See https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/556621 for details.


It is an issue with backup and moving VM guests.

Foolish that I have to work with a 1.3 TB file, when ther's only ex. 350 GB data in it.

When installing a *******, Thin Provisioning works as intended.

I will now test 8.04 Hardy LTS, just to be sure.

It should not be THAT large. For a 1.5 TB virtual disk, there should be around 24 GB worth of inode tables written during a normal format. If you then add 350 gb of files to it I would expect the backing file to grow to around 400-450 gb.

Also the option I mentioned is new, so it won't work in hardy.

[fveggerby]

It should not be THAT large. For a 1.5 TB virtual disk, there should be around 24 GB worth of inode tables written during a normal format. If you then add 350 gb of files to it I would expect the backing file to grow to around 400-450 gb.

AAAAhhhhh, I have only "testet" up to around 10 GB or so, then broke install.
Appearently, I'm just impatient. :)

[fveggerby]

Jep, that was the problem.
Me, being impatient.

clean install, 28.3 GB, and about an hour.

"Problem" solved.

[psusi]

Jep, that was the problem.
Me, being impatient.

clean install, 28.3 GB, and about an hour.

"Problem" solved.

Yep, the lazy_itable_init option should get that hour down to a minute or so ;)

I have a 1.5 TB disk that took 20 minutes to format before I used that option, which dropped it to about 10-15 seconds.