Koozali.org: home of the SME Server
Obsolete Releases => SME Server 8.x => Topic started by: bterlouw on March 20, 2012, 07:30:02 PM
-
I recently brought a new SME8b7 machine on line to replace an antiquated SME7.5.1 computer with minimal free space. I thought everything went fine, but when I looked on a windows machine at the available free space (old computer was 32G drive with 1G free, new computer registered 32G with 2G free) I still had free space issues. The new machine has dual 500G drives in it (should be RAID1 and acts as such). Knowing that one must resize the volumes after such a restore (by workstation on to the new machine) I then ran the following commands:
mdadm --grow /dev/md2 --size=max
pvresize /dev/md2
lvresize -l +100%FREE main/root
resizefs /dev/main/root
The first two seemed to run fine and changed things. The third one gives a message that there is no change; the last one then does nothing as well. I tried to see about free space, but it claims there is none to capture. I am at a loss, so thanks for your help.
Possibly informative outputs:
#df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/main-root
468001888 30340376 413504944 7% /
/dev/md1 101018 12258 83544 13% /boot
tmpfs 2068796 0 2068796 0% /dev/shm
#df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/main-root
447G 29G 395G 7% /
/dev/md1 99M 12M 82M 13% /boot
tmpfs 2.0G 0 2.0G 0% /dev/shm
#vgdisplay
--- Volume group ---
VG Name main
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 6
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 2
Open LV 2
Max PV 0
Cur PV 1
Act PV 1
VG Size 465.66 GB
PE Size 32.00 MB
Total PE 14901
Alloc PE / Size 14901 / 465.66 GB
Free PE / Size 0 / 0
VG UUID kxfKEu-UmDI-kOV7-fIrH-nnAO-ip9d-6BrQUe
#lvdisplay
--- Logical volume ---
LV Name /dev/main/root
VG Name main
LV UUID NaWa5s-1Zk9-5sfJ-R2yb-vSL3-7WW7-F3SKLJ
LV Write Access read/write
LV Status available
# open 1
LV Size 460.75 GB
Current LE 14744
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0
--- Logical volume ---
LV Name /dev/main/swap
VG Name main
LV UUID m6oaeT-1JOR-cma2-CnMo-pz7z-HRf8-5qkwTi
LV Write Access read/write
LV Status available
# open 1
LV Size 4.91 GB
Current LE 157
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1
#pvdisplay
--- Physical volume ---
PV Name /dev/md2
VG Name main
PV Size 465.66 GB / not usable 3.25 MB
Allocatable yes (but full)
PE Size (KByte) 32768
Total PE 14901
Free PE 0
Allocated PE 14901
PV UUID p6EDEa-kzzv-mmn5-ufdJ-RT45-WOA3-XDlbhK
#lvm pvscan
PV /dev/md2 VG main lvm2 [465.66 GB / 0 free]
Total: 1 [465.66 GB] / in use: 1 [465.66 GB] / in no VG: 0 [0 ]
#fdisk -l /dev/sda
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 fd Linux raid autodetect
/dev/sda2 14 60801 488279610 fd Linux raid autodetect
#fdisk -l /dev/sdb
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 13 104391 fd Linux raid autodetect
/dev/sdb2 14 60801 488279610 fd Linux raid autodetect
-
I recently brought a new SME8b7 machine on line to replace an antiquated SME7.5.1 computer with minimal free space. I thought everything went fine, but when I looked on a windows machine at the available free space (old computer was 32G drive with 1G free, new computer registered 32G with 2G free) I still had free space issues. The new machine has dual 500G drives in it (should be RAID1 and acts as such). Knowing that one must resize the volumes after such a restore (by workstation on to the new machine) I then ran the following commands:
Not so. You do not have to resize after a restore from workstation backup. Besides, your df -h shows that you have ample free space on the drive. Check whether you have quota enabled for the user login into this server from the Window box, and disable or adjust to a larger value.
-
Thanks for the quick reply.
There are no quotas enabled on the machine. The directory is a public share. I agree that all the linux outputs seem to show that there is lots of free space, but in windows explorer on several machines, I only see a 32.8G drive with 1.9G free.
But wait, I just tried to check the free space from an XP system and it shows fine. Apparently my Win7 systems are at fault. I apologize for the unnecessary problem.
Thanks again for the help.
-
But wait, I just tried to check the free space from an XP system and it shows fine. Apparently my Win7 systems are at fault. I apologize for the unnecessary problem.
No unnecessary problem, this is what we are here for, giving a hand and ensuring that bugs are identified. Just checked a Win7 Pro box on a network with an 8b7 server, I can see 700GB free out of 900GB total space. Please post here your finding when you find out what is the cause of your issue with WIN7.
Thanks.
-
The problem was with the DNS cache on the Win7 machines.
During my install, I had renamed and IP addressed the SME7 machine, but kept it on the network (in case I needed to access anything). I then had restored the backup on the new SME8 machine and then rebooted (thus taking the initial host name and IP address). Apparently the Win7 machines followed the SME7 machine to its new IP and ignored its new host name (the mapped drives still listed themselves as the old host name but were definitely going to the old, renamed machine).
The fix was shutting down the old machine. On some Win7 machines I had to manually flush the DNS, others fixed themselves.