Bug #2497
closed
DFBSD v3.2.2-RELEASE - Available space not correctly computed after 'hammer volume-add'
Description
Hi,
After hammer volume-add it seems that the available space isn't computed correctly.
testbox2# df -h
Filesystem Size Used Avail Capacity Mounted on
ROOT 17G 2.7G 14G 15% /
devfs 1.0K 1.0K 0B 100% /dev
/dev/serno/QM00001.s1a 756M 177M 519M 25% /boot
/pfs/@-1:00001 17G 2.7G 14G 15% /var@-1:00002 17G 2.7G 14G 15% /tmp
/pfs/
/pfs/@-1:00003 17G 2.7G 14G 15% /usr@-1:00004 17G 2.7G 14G 15% /home
/pfs/
/pfs/@-1:00005 17G 2.7G 14G 15% /usr/obj@-1:00006 17G 2.7G 14G 15% /var/crash
/pfs/
/pfs/@-1:00007 17G 2.7G 14G 15% /var/tmp@-1:00001 17G -6.0G 23G -35% /var
procfs 4.0K 4.0K 0B 100% /proc
testbox2# hammer volume-add /dev/da0s1a /
testbox2# df -h
Filesystem Size Used Avail Capacity Mounted on
ROOT 17G -6.0G 23G -35% /
devfs 1.0K 1.0K 0B 100% /dev
/dev/serno/QM00001.s1a 756M 177M 519M 25% /boot
/pfs/
/pfs/@-1:00002 17G -6.0G 23G -35% /tmp@-1:00003 17G -6.0G 23G -35% /usr
/pfs/
/pfs/@-1:00004 17G -6.0G 23G -35% /home@-1:00005 17G -6.0G 23G -35% /usr/obj
/pfs/
/pfs/@-1:00006 17G -6.0G 23G -35% /var/crash@-1:00007 17G -6.0G 23G -35% /var/tmp
/pfs/
procfs 4.0K 4.0K 0B 100% /proc
Cheers,
Antonio Huete
Updated by tuxillo about 10 years ago
- Description updated (diff)
- Status changed from New to In Progress
- Assignee set to tuxillo
Grab!
Updated by tuxillo about 10 years ago
- Status changed from In Progress to Feedback
- Target version changed from 3.8 to 3.6.1
- % Done changed from 0 to 100
Should be fixed in 63eefcf7775a18787490dc9fff3f8ce6657015af.