Re: which files took the space

2016-03-07 Thread Adam Wilson
On Fri, 04 Mar 2016 08:11:43 +0100 Frédéric Marchal wrote: > On Friday 04 March 2016 07:18:59 Adam Wilson wrote: > > On Fri, 4 Mar 2016 04:03:01 +1100 Andrew McGlashan > > > > wrote: > > > On 4/03/2016 3:07 AM, Adam Wilson wrote: > > > > On Fri, 4 Mar 2016 03:03:53 +1100 Andrew McGlashan > > >

Re: which files took the space

2016-03-06 Thread Pascal Hambourg
David Wright a écrit : > On Sat 05 Mar 2016 at 21:18:55 (+0100), Pascal Hambourg wrote: >> David Wright a écrit : >>> You can't create files on an unmounted filesystem. >> Of course you can, with the adequate tools. For instance mtools for FAT, >> e2tools for ext2, ntfs-3g (previoulsy ntfsprogs) fo

Re: which files took the space

2016-03-05 Thread David Wright
On Sat 05 Mar 2016 at 21:18:55 (+0100), Pascal Hambourg wrote: > David Wright a écrit : > > > > You can't create files on an unmounted filesystem. > > Of course you can, with the adequate tools. For instance mtools for FAT, > e2tools for ext2, ntfs-3g (previoulsy ntfsprogs) for NTFS. Thank you f

Re: which files took the space

2016-03-05 Thread Pascal Hambourg
David Wright a écrit : > > You can't create files on an unmounted filesystem. Of course you can, with the adequate tools. For instance mtools for FAT, e2tools for ext2, ntfs-3g (previoulsy ntfsprogs) for NTFS.

Re: which files took the space

2016-03-05 Thread Pascal Hambourg
to...@tuxteam.de a écrit : > > It was perceived as an artificial limitation which has no place in > the kernel. Actually, I can conceive use cases for mount shadowing > the content of a directory. Typically : /dev

Re: which files took the space

2016-03-05 Thread Rick Thomas
On Mar 4, 2016, at 5:39 AM, Gene Heskett wrote: > On Friday 04 March 2016 03:39:03 jdd wrote: > >> Le 04/03/2016 08:38, to...@tuxteam.de a écrit : >>> If memory serves, long, long time ago, "mount" (the system call) >>> refused to comply unless the directory was empty (kernel 2.6.mumble; >>> so

Re: which files took the space

2016-03-04 Thread Jörg-Volker Peetz
The list seems nowadays to have a very short memory ;-) A similar problem was discussed last time hardly a month ago: https://lists.debian.org/debian-user/2016/02/threads.html#00267 So in order to avoid the pit you fall into you could've used a command like du /home -hx --max-depth=1 Regards,

Re: which files took the space

2016-03-04 Thread Gene Heskett
On Friday 04 March 2016 03:39:03 jdd wrote: > Le 04/03/2016 08:38, to...@tuxteam.de a écrit : > > If memory serves, long, long time ago, "mount" (the system call) > > refused to comply unless the directory was empty (kernel 2.6.mumble; > > so long ago. Expect bit flips and glitches in my wetware,

Re: which files took the space

2016-03-04 Thread jdd
Le 04/03/2016 08:38, to...@tuxteam.de a écrit : If memory serves, long, long time ago, "mount" (the system call) refused to comply unless the directory was empty (kernel 2.6.mumble; so long ago. Expect bit flips and glitches in my wetware, yadda). if it existed, it's much older than that, neve

Re: which files took the space

2016-03-04 Thread tomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Mar 03, 2016 at 11:17:19PM -0500, Cindy-Sue Causey wrote: > On 3/3/16, Andrew McGlashan wrote: > > > > On 4/03/2016 3:07 AM, Adam Wilson wrote: > >> On Fri, 4 Mar 2016 03:03:53 +1100 Andrew McGlashan > >> wrote: > >>> It also may have been fi

Re: which files took the space

2016-03-03 Thread jdd
Le 04/03/2016 08:11, Frédéric Marchal a écrit : It can happen with /boot or /home. Mistakenly copying files to an unmounted drive copies the files to the underlying file system, in the directory that usually serves as the mount point for the external file system. Once /boot or /home is mounted,

Re: which files took the space

2016-03-03 Thread Frédéric Marchal
On Friday 04 March 2016 07:18:59 Adam Wilson wrote: > On Fri, 4 Mar 2016 04:03:01 +1100 Andrew McGlashan > > wrote: > > On 4/03/2016 3:07 AM, Adam Wilson wrote: > > > On Fri, 4 Mar 2016 03:03:53 +1100 Andrew McGlashan > > > > > > wrote: > > >> It also may have been files in the file system, but

Re: which files took the space

2016-03-03 Thread Gene Heskett
On Thursday 03 March 2016 23:18:59 Adam Wilson wrote: > On Fri, 4 Mar 2016 04:03:01 +1100 Andrew McGlashan > > wrote: > > On 4/03/2016 3:07 AM, Adam Wilson wrote: > > > On Fri, 4 Mar 2016 03:03:53 +1100 Andrew McGlashan > > > > > > wrote: > > >> It also may have been files in the file system, bu

Re: which files took the space

2016-03-03 Thread David Wright
On Fri 04 Mar 2016 at 07:18:59 (+0300), Adam Wilson wrote: > On Fri, 4 Mar 2016 04:03:01 +1100 Andrew McGlashan > wrote: > > > On 4/03/2016 3:07 AM, Adam Wilson wrote: > > > On Fri, 4 Mar 2016 03:03:53 +1100 Andrew McGlashan > > > wrote: > > >> It also may have been files in the file system, but

Re: which files took the space

2016-03-03 Thread David Wright
On Thu 03 Mar 2016 at 23:17:19 (-0500), Cindy-Sue Causey wrote: > On 3/3/16, Andrew McGlashan wrote: > > > > On 4/03/2016 3:07 AM, Adam Wilson wrote: > >> On Fri, 4 Mar 2016 03:03:53 +1100 Andrew McGlashan > >> wrote: > >>> It also may have been files in the file system, but where another file >

Re: which files took the space

2016-03-03 Thread Adam Wilson
On Fri, 4 Mar 2016 04:03:01 +1100 Andrew McGlashan wrote: > > > On 4/03/2016 3:07 AM, Adam Wilson wrote: > > On Fri, 4 Mar 2016 03:03:53 +1100 Andrew McGlashan > > wrote: > >> It also may have been files in the file system, but where another > >> file system mount hides them > > > > What

Re: which files took the space

2016-03-03 Thread Cindy-Sue Causey
On 3/3/16, Andrew McGlashan wrote: > > On 4/03/2016 3:07 AM, Adam Wilson wrote: >> On Fri, 4 Mar 2016 03:03:53 +1100 Andrew McGlashan >> wrote: >>> It also may have been files in the file system, but where another file >>> system mount hides them >> >> What does this mean? Mounts overlapping

Re: which files took the space

2016-03-03 Thread Andrew McGlashan
On 4/03/2016 3:07 AM, Adam Wilson wrote: > On Fri, 4 Mar 2016 03:03:53 +1100 Andrew McGlashan > wrote: >> It also may have been files in the file system, but where another file >> system mount hides them > > What does this mean? Mounts overlapping and hiding other mounts? > > Explain, plea

Re: which files took the space

2016-03-03 Thread jdd
Le 03/03/2016 17:03, Andrew McGlashan a écrit : On 3/03/2016 1:51 PM, lina wrote: I figured out, there are so many hidden files. It also may have been files in the file system, but where another file system mount hides them A. or file in use deleted but not released... like virtual mac

Re: which files took the space

2016-03-03 Thread Adam Wilson
On Fri, 4 Mar 2016 03:03:53 +1100 Andrew McGlashan wrote: > > > On 3/03/2016 1:51 PM, lina wrote: > > I figured out, there are so many hidden files. > > It also may have been files in the file system, but where another file > system mount hides them What does this mean? Mounts overlapping

Re: which files took the space

2016-03-03 Thread Andrew McGlashan
On 3/03/2016 1:51 PM, lina wrote: > I figured out, there are so many hidden files. It also may have been files in the file system, but where another file system mount hides them A.

Re: which files took the space

2016-03-03 Thread Jochen Spieker
lina: > > how do I know which files mounted on the /home. In the future you can install and use 'ncdu'. It is a nice terminal program that calculates directory sizes and allows you to easily see what occupies the most disk space. J. -- I like my Toyota RAV4 because of the commanding view of the

Re: which files took the space

2016-03-02 Thread lina
I figured out, there are so many hidden files. Thanks, On Thu, Mar 3, 2016 at 10:38 AM, lina wrote: > Hi, > > I did a simple check: > > $ df -h > Filesystem Size Used Avail Use% Mounted on > /dev/sda5 658M 408M 217M 66% / > /dev/sda4 213M 64M 139M 32% /boot > /dev/sda7