I recently installed 11.2 with a 5.58Gb swap partition. I soon realized that due the efficiency of the openSUSE operating system, this swap partition was unused. So I unmounted and deleted it, resizing my /home partition to swallow up the freed space. The Yast partitioning tool gave an error at the time, sorry I don’t remember exactly what it said. When I rebooted the partitioning tool shows the correct information for the /home partition, 43Gb (was 37Gb) and no swap partition. Dolphin however, shows the device usage for home folder “mounted on: /home” to be 37.7Gb. Is there an /etc/fstab or /etc/mtab entry I need to edit to get the correct information in Dolphin?
Two possibilities: YaST is using the older k=1000 convention and KDE the newer k=1024 convention, though not sure that will explain the whole discrepancy, and YaST will include everything whereas Dolphin may exclude those parts of the disk concerned with administering the filesystem.
Was /home also unmounted at the time of the attempted resize?
Perhaps YAST waits for a reboot to to do the resize on an unmouted partition,Ido not know the YAST partitioner.
You should not be able to resize a mounted partition.
I notice you have rebooted,have you forced a file system check?
And of course,what does fdisk -l tell us.
And not only
fdisk -l
but also
mount
and
df
linux-tuxs:/home/chris # fdisk -l
Disk /dev/sdc: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xa8a8a8a8
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 4001 32138001 83 Linux
/dev/sdc2 4002 9730 46012711+ 83 Linux
linux-tuxs:/home/chris # mount
/dev/sdc1 on / type ext4 (rw,acl,user_xattr)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
/dev/sdc2 on /home type ext4 (rw)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
securityfs on /sys/kernel/security type securityfs (rw)
linux-tuxs:/home/chris # df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sdc1 31633064 8200384 21825780 28% /
udev 510148 200 509948 1% /dev
/dev/sdc2 39531116 6513436 31009556 18% /home
On 03/04/2010 02:46 PM, Euripides wrote:
>
> I recently installed 11.2 with a 5.58Gb swap partition. I soon realized
> that due the efficiency of the openSUSE operating system, this swap
> partition was unused. So I unmounted and deleted it, resizing my /home
> partition to swallow up the freed space. The Yast partitioning tool gave
> an error at the time, sorry I don’t remember exactly what it said. When
> I rebooted the partitioning tool shows the correct information for the
> /home partition, 43Gb (was 37Gb) and no swap partition. Dolphin however,
> shows the device usage for home folder “mounted on: /home” to be 37.7Gb.
> Is there an /etc/fstab or /etc/mtab entry I need to edit to get the
> correct information in Dolphin?
>
>
Truth is /swap does get used and usually 512M-1GB is more than enough,
but its also true that you can get away without a swap file with these
later kernels.
You can allocate a file and use that as /swap instead of partitioning,
however, the partitioning on initial install is better.
mkdir /moreswap
mkfile 1024m /moreswap
/usr/sbin/swap -a /moreswap/swapFile
Then add the new swap to /etc/fstab
/moreswap/ swap swap defaults 0 0
Still better to allocate or use the default /swap created during the
initial install though.
by forced, do mean without unmounting? scary:O
Thanks (between CODE tags it would have been better readable).
fdisk shows that there are two partitions that fill up the disk neatly. It also shows that sdc2 is 46012711 blocks
df shows 39531116 1k blocks. This looks as if only 85% became available.
OTH sdc1 has 31633064 out of 32138001, which is 98%.
Normaly 5% is reserved for calamities and thus 95% would be available. Now the fact that you used YaST for it and forgot what it reported brings us to the point that we do not realy know what happened.
I personaly would have made a backup of /home, then repartitioned using fdisk, then gnerated a new fs on sdc2 using mkfs, then copy back from the backup, but I do not know if YaST somewhere logs in a clear way what it does.
You could do a
tune2fs -l /dev/sda2
and look at the Block count and* Reserved block count* items to see if he scond is 5% of the first. Also other items in that listing could give you a clue.
When you want to be sure that the partition and its fs are in the state you want them, you could do as I would do (old fashioned, but a way I understand instead of the shady way a GUI functions): backup, mkfs anew, load back.
Edit: and of course an fsck works only on the unmounuted fs. Better go to runlevel 1, umount, fsck, mount, back to runlevel 5.
GParted 0.4.7
Libparted 1.9.0
Check and repair file system (ext4) on /dev/sdc2 00:00:08 ( SUCCESS )
calibrate /dev/sdc2 00:00:00 ( SUCCESS )
path: /dev/sdc2
start: 64276065
end: 156301487
size: 92025423 (43.88 GiB)
check file system on /dev/sdc2 for errors and (if possible) fix them 00:00:04 ( SUCCESS )
e2fsck -f -y -v /dev/sdc2
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
3265 inodes used (0.13%)
41 non-contiguous files (1.3%)
3 non-contiguous directories (0.1%)
of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 3246/4
1786492 blocks used (17.79%)
0 bad blocks
1 large file
2894 regular files
357 directories
0 character device files
0 block device files
0 fifos
0 links
5 symbolic links (5 fast symbolic links)
0 sockets
3256 files
e2fsck 1.41.9 (22-Aug-2009)
grow file system to fill the partition 00:00:04 ( SUCCESS )
resize2fs /dev/sdc2
Resizing the filesystem on /dev/sdc2 to 11503177 (4k) blocks.
The filesystem on /dev/sdc2 is now 11503177 blocks long.
resize2fs 1.41.9 (22-Aug-2009)
========================================
here is a quote from man e2fsck
-f Force checking even if the file system seems clean.
I notice you also later ran this.
e2fsck -f -y -v /dev/sdc2
To reinforce this , quote from HCW earlier in this thread.
Edit: and of course an fsck works only on the unmounuted fs. Better go to runlevel 1, umount, fsck, mount, back to runlevel 5.
What ran was gparted, as root, unmounted sdc2 then checked it. My post was the detailed output of gparted.
here is a quote from man e2fsck
-f Force checking even if the file system seems clean.
This answers the question of what I meant by forced. I should however have been more specific.