> 1. I don't keep many files open forever, they are duly closed after being
> used. Many created, filled up, closed, uploaded, and erased.
> 2. FIles get created on /home
> 3. / get overflown, not /home
> 4. If your explanation were correct, /home would have been overflown.
Sergei, you yourself h
** Changed in: e2fsprogs (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1319667
Title:
root file system 100% full, goes 52% after reboot
To manage notification
1. I don't keep many files open forever, they are duly closed after
being used. Many created, filled up, closed, uploaded, and erased.
2. FIles get created on /home
3. / get overflown, not /home
4. If your explanation were correct, /home would have been overflown.
5. I think you explanation (no
strace dies as well
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1319667
Title:
root file system 100% full, goes 52% after reboot
To manage notifications about this bug go to:
https://bugs.launchp
If you have processes keeping a file open, the space doesn't get
reclaimed until the file is closed or the process is killed. Obviously,
the latter tends to happen when you reboot a system. This is standard
practice going back to 1970's and Unix; in fact, it is required by the
POSIX standard.
W
now 5 hours from my initial report
#df -h
hangs *indefinetely*,
whereas ncdu -x from / shows about 1/2 fullness (my root patition / is
about 23G)
9,3GiB [##] /usr
