After that last operation I booted into Karmic and used it's Gparted to
run a file system check. My first observation was that it showed 26+GB
used which I knew was incorrect. After performing the fsck it showed
11+GB used which is correct. No data was lost, Jaunty still boots fine.
These are the results of the Karmic fsck if it's helpful:
GParted 0.4.5
Libparted 1.8.8.1.159-1e0e
Check and repair file system (ext3) on /dev/sda6 00:01:17 ( SUCCESS )
calibrate /dev/sda6 00:00:03 ( SUCCESS )
path: /dev/sda6
start: 77095998
end: 149147459
size: 72051462 (34.36 GiB)
check file system on /dev/sda6 for errors and (if possible) fix them 00:01:03
( SUCCESS )
e2fsck -f -y -v /dev/sda6
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
21522 inodes used (1.75%)
729 non-contiguous files (3.4%)
19 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 3471/232/0
2888335 blocks used (58.95%)
0 bad blocks
2 large files
18458 regular files
3013 directories
0 character device files
0 block device files
0 fifos
0 links
42 symbolic links (26 fast symbolic links)
0 sockets
--------
21513 files
e2fsck 1.41.9 (22-Aug-2009)
grow file system to fill the partition 00:00:11 ( SUCCESS )
resize2fs /dev/sda6
Resizing the filesystem on /dev/sda6 to 9006432 (4k) blocks.
The filesystem on /dev/sda6 is now 9006432 blocks long.
resize2fs 1.41.9 (22-Aug-2009)
Many thanks to Colin Watson for pointing out that this was unrelated to
the ubiquity bug.
I'll be glad to follow up on this as needed.
--
Lucid Gparted fails to create multiple partitions
https://bugs.launchpad.net/bugs/510179
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
