On Mon 09 May 2016 at 14:50:06 +0200, [email protected] wrote: > On Mon, May 09, 2016 at 08:41:59AM -0400, Haines Brown wrote: > > On Mon, May 09, 2016 at 11:05:13AM +0000, Andy Smith wrote: > > > Hi Haines, > > > > > I had thought that the "sde1" in your ncdu output was some sort of > > > header representing the / device, but having installed ncdu and run > > > it myself I am inclined to agree with Juergen that it is actually a > > > file. > > > > And so it is. I must have seen /sde1, but it failed to register on my > > octogenarian brain. I moved it into storage and my full disk problem is > > gone. Hard to know what that file is. The file command says it is data. > > It may be an ISO. I'll eventually delete it. > > A cheap shot: try to mount it. Either as loopback: > > mount -o loop /sde1 /mnt > > or by dd'ing it first to a suitable storage (e.g. a stick). > > If that suceeds, then it is a file system image *and* you can nose > around in the mount directory (/mnt in the above example) to refresh > your memory. > > Of course you gotta do that as root, either by sudo magic or whatever.
Not necessarily; udisksctl (install udisks2) and udevil are two programs which will do this for a user.
