Hi Haines, On Mon, May 09, 2016 at 06:43:59AM -0400, Haines Brown wrote: > I had been inserting a sequence of USB keys to see what was on them, and > pretty sure the sde1 interface was used at some point. But no keys are > inserted at present. I also just did a cross installation onto an
[…] > $ ls -la /sys/block/sde > lrwxrwxrwx 1 root root 0 May 9 05:30 /sys/block/sde -> > > ../devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3.3/1-3.3:1.0/host7/target7:0:0/ > \ > 7:0:0:1/block/sde So it seems like sde is/was a USB block device. 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. > Juergen suggested deleting /dev/sde1 it after backing it up. That was my > first inclination, but kinda hard to do if /dev/sde1 is not visible. In your ncdu output it looked like you ran it while / was your current directory, and the output it gave was just "sde1", not "/dev/sde1". So have a look for the file /sde1. Perhaps you have tried to write an image to a USB key at /dev/sde1 but done a typo and actually written to /sde1, thus creating that file? Certainly if I do this: $ sudo du if=/dev/zero of=/sde1 bs=1M count=100 $ sudo ncdu -rx / then I end up with a line of output that looks like what you provided. So, are you sure there is not just a regular file at /sde1 (not in /dev)? Cheers, Andy -- http://bitfolk.com/ -- No-nonsense VPS hosting
signature.asc
Description: Digital signature
