Bug 7941 - error size disk
Summary: error size disk
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard: 3beta1
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2012-11-01 06:15 CET by Arnaud Vacquier
Modified: 2013-01-28 06:10 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
eror size (239.85 KB, image/png)
2012-11-01 06:15 CET, Arnaud Vacquier
Details

Description Arnaud Vacquier 2012-11-01 06:15:59 CET
Created attachment 3022 [details]
eror size

hi,

my harddrive is 150Go size but when I look at the properties, there are 140.7To :O

thank you

System : Mageia 3 64bits on Gnome 3.6
Comment 1 Manuel Hiebel 2012-11-11 00:35:09 CET
what does said df ?

it seems you have two disk and the two are mounted on / ?

Keywords: (none) => NEEDINFO

Comment 2 Arnaud Vacquier 2012-11-12 12:50:09 CET
hi,

No, it is my usb key (sdb) the other disk, for df :


[root@localhost ~]# df
Sys. fich.     Taille Util. Dispo Uti% Monté sur
rootfs            12G  5,0G  6,3G  45% /
devtmpfs         2,0G     0  2,0G   0% /dev
tmpfs            2,0G  412K  2,0G   1% /dev/shm
tmpfs            2,0G  824K  2,0G   1% /run
/dev/sda1         12G  5,0G  6,3G  45% /
tmpfs            2,0G     0  2,0G   0% /sys/fs/cgroup
none             2,0G   88K  2,0G   1% /tmp
/dev/sda6        132G  1,5G  130G   2% /home


thank you
Arnaud Vacquier 2012-12-21 05:11:15 CET

Whiteboard: (none) => 3beta1

Comment 3 roelof Wobben 2013-01-07 15:10:53 CET
@Arnaud : Is this bug still valid on Mageia 2 or Cauldron ?

Roelof

CC: (none) => r.wobben

Comment 4 Arnaud Vacquier 2013-01-07 21:35:38 CET
i can say that only the 19 january, i haven't my gnome computer
Comment 5 roelof Wobben 2013-01-07 21:41:09 CET
Oke, We will wait till then.
Thanks for the message. 

Roelof
Comment 6 Arnaud Vacquier 2013-01-28 06:10:14 CET
run good now after update

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.