Thanks for this information. So what should I do? On Fri, Aug 19, 2016 at 12:34 PM, Carruth, Rusty wrote: > Did you log out and back in after mounting the 2nd drive? > > > > If you added the drive and then ran a GUI-based program there is a > better-than-0 chance that your GUI still has a hold on the old /home folder. > > > > Let me try to explain. > > > > Before mounting the new drive on /home, if you do ‘cd /home;ls -lid .;ls > -lid /home’ you might see number in the first column like 1213451 (for both > ls outputs) - that is the i-node for the current /home dir and the current > dir. > > Now, leave that window alone, switch to a new window, and mount the new > drive. In that new window, do an ls -lid /home and you will (almost > certainly) see a different number, say 1122. > > However, if you go back to that first window and say ls -lid . you’ll see > 1213451. Now, in that same window, type ‘ls -lid /home’ and you’ll see the > 1122! > > > > How is that??? . and /home are supposed to be the same! > > > > Well, no. your Bash shell did a cd /home and got the inode 1213451. Now > it (IIRC) keeps that inode open. When you mount that new drive on /home, > your shell still has the old /home dir open - and anything going from . > will get the old inode on the original drive! So ‘.’ Is inode 1213451, and > /home is inode 1122. In fact, ./../home will be inode 1122, as will > ../home. > > > > Here is an example: > > > > Window 1: > > oakgatecontrol ~ # mkdir demo > > oakgatecontrol ~ # ls -lid demo > > 9973488 drwxr-xr-x 2 root root 4096 Aug 19 09:27 demo > > oakgatecontrol ~ # mount -o loop sdc.dd demo # here is the > mount I did, referenced below. > > oakgatecontrol ~ # ls -lid demo/ > > 2 drwxr-xr-x 3 root root 1024 Aug 19 09:27 demo/ > > oakgatecontrol ~ # > > > > window 2: > > > > oakgatecontrol ~ # ls -lid demo > > 9973488 drwxr-xr-x 2 root root 4096 Aug 19 09:27 demo > > oakgatecontrol ~ # cd demo > > oakgatecontrol demo # ls -lid . ../demo # this is BEFORE I mounted a > filesystem on demo. > > 9973488 drwxr-xr-x 2 root root 4096 Aug 19 09:27 . > > 9973488 drwxr-xr-x 2 root root 4096 Aug 19 09:27 ../demo > > oakgatecontrol demo # ls -lid . ../demo # this is AFTER I did the > mount above. > > 9973488 drwxr-xr-x 2 root root 4096 Aug 19 09:27 . > > 2 drwxr-xr-x 3 root root 1024 Aug 19 09:27 ../demo > > oakgatecontrol demo # > > > > > > Now, please don’t let the fact that I used a file which I’d made into a > filesystem confuse you - the effects are identical if you use a block > special device. > > > > In fact, if I create a file inside the ‘demo’ which is NOT mounted, then > mount the filesystem on demo, that 2nd window sees this: > > > > oakgatecontrol demo # ls -lid . ../demo ; ls -l . ../demo > > 9973488 drwxr-xr-x 2 root root 4096 Aug 19 09:32 . > > 2 drwxr-xr-x 3 root root 1024 Aug 19 09:27 ../demo > > .: > > total 0 > > -rw-r--r-- 1 root root 0 Aug 19 09:32 foobar > > > > ../demo: > > total 12 > > drwx------ 2 root root 12288 Aug 19 09:27 lost+found > > oakgatecontrol demo # > > > > (Unfortunately, this email will not make it to the PLUG list, since I can > no longer email from the email address it uses to send these to me. Real > Soon Now I will fix that, but for now you’re the only one who will see it, > unless you reply all) > > > > Rusty > > > > *From:* plug-discuss-bounces@lists.phxlinux.org [mailto: > plug-discuss-bounces@lists.phxlinux.org] *On Behalf Of *Michael > *Sent:* Friday, August 19, 2016 6:02 AM > *To:* PLUG > *Subject:* other drive > > > > I set my computer up with home on it's own drive. I discovered last night > (when I was my gigapixel rendering) the setup is screwed up somehow (I came > close to running out of disk space and df says there is a LOT of space on > home). Could someone tell me where I screwed up and how to fix this? Well > looking at df again it says /home is using 50 gig which indicates it is > being used. Why did I run out of room? > > > > -- > > :-)~MIKE~(-: > -- :-)~MIKE~(-: