On 10/22/2010 03:26 PM, Fennix wrote:
On Sat, Oct 23, 2010 at 4:12 AM, alan <alan@xxxxxxxxxxxxxx>
wrote:
On Fri, 22 Oct 2010, Kevin Martin wrote:
>
>
> On 10/22/2010 03:10 PM, Terry Polzin wrote:
>> On Fri, 2010-10-22 at 14:59 -0500, Kevin Martin
wrote:
>>> I've been building out a new laptop and trying
to copy over the contents of my userspace from my old laptop
to my new laptop. I
>>> keep running out of space on my new laptop even
though my home directory is only 6.6Gb and the userspace
(/home) on the new laptop
>>> hase 156Gb of space. So I cleared out
everything from my /home directory on my new machine and now
I see this:
>>>
>>> [root@ktmtoshiba /]# du -sh home
>>> 24K home
>>>
>>> [root@ktmtoshiba /]# df -h
>>> Filesystem Size Used Avail Use%
Mounted on
>>> /dev/mapper/vg_ktmtoshiba-lv_root
>>> 50G 7.2G 40G 16% /
>>> tmpfs 1.9G 0 1.9G 0%
/dev/shm
>>> /dev/sda5 485M 28M 432M 6%
/boot
>>> /dev/mapper/vg_ktmtoshiba-lv_home
>>> 164G 188M 155G 1%
/home
>>>
>>>
>>> How can du show that home is 24k (which is
probably ok since there are no files in there, just my home
directory and lost+found)
>>> while df shows /home as having 188M used?
>>>
>>> Any pertinent thoughts welcome.
>>>
>>> Thanks.
>>>
>>> Kevin
>> Block size vs. file size
>>
> No matter how you cut it 188Mb doesn't equal 24K.
Something seems funky here.
How much space is taken up by the filesystem journal?
--
Truth is stranger than fiction because fiction has to make
sense.
How about hidden directories caching temporary data for any (and
every) application you have installed? Firefox, Opera, Chromium,
Open Office, Evolution, and any of a myriad applications you might
be using?
/fennix
When you say hidden directories I assume you mean . (dot)
directories and there are none. When I cleaned out my new home
directory I made sure to "/bin/rm -rf *" and "/bin/rm -rf .[a-z]*"
so it was completely empty.
And as far as I can tell the size of the journal for the device is
134217728 or about 128Mb. I get that this way:
[root@ktmtoshiba /]# mount
/dev/mapper/vg_ktmtoshiba-lv_root on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs
(rw,rootcontext="system_u:object_r:tmpfs_t:s0")
/dev/sda5 on /boot type ext4 (rw)
/dev/mapper/vg_ktmtoshiba-lv_home on /home type ext4 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
capifs on /dev/capi type capifs (rw,mode=0666)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
[root@ktmtoshiba /]# tune2fs -l /dev/mapper/vg_ktmtoshiba-lv_home |
awk '/Journal.inode/ {print $3}'
8
[root@ktmtoshiba /]# debugfs -R "stat <8>"
/dev/mapper/vg_ktmtoshiba-lv_home 2>&1| awk '/Size: / {print
$6}'|head -1
134217728
Then, apparently I divide that number by the size of 1Mb (2^20 or
1048576) and get 128 (exactly). So I can see where df is reporting,
at least in part, the size of the journal while du is not. Clear as
mud! ;-)
Thanks.
Kevin
|
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
