[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#840184: marked as done (df and du shows different size)

Your message dated Sat, 15 May 2021 02:25:36 -0700 (PDT)
with message-id <609f9390.1c69fb81.20a19.6960@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #840184,
regarding df and du shows different size
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
840184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840184
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-3.16.0-4-amd64
Version: 3.16.36-1+deb8u1

Hello!
Usually df -h and du -hs shows the same used space. But now I have a problem. I am using two SSD for a cache. Script using df command, all time writes and deletes files. There are no such problem with wheezy kernels. 

df -h
/dev/sdc1          237G         178G   47G           80% /megastorage1
/dev/sdb1          237G         177G   48G           79% /megastorage2

du -hs /megastorage1
24G     /megastorage1

du -hs /megastorage2
23G     /megastorage2


 mount | grep megastorage
/dev/sdc1 on /megastorage1 type ext4 (rw,noatime,data=ordered)
/dev/sdb1 on /megastorage2 type ext4 (rw,noatime,data=ordered)

--- End Message ---
--- Begin Message --- 
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---
Reply to: