you get that message while some process has a file open in that
filesystem.  eg perhaps your shell had it's current directory in there.  or
something you launched.  or possibly a daemon.  once the file/directories
are no longer busy the umount will proceed.  otoh you could just shrug,
remove/change the filesystem definition in /etc/fstab and reboot.  sounds
like that's where you're headed anyway..


On 28 December 2014 at 15:49, Jeff Jensen <jjensen at apache.org> wrote:

> I meant to note that trying the obvious has this issue:
> # umount /home
> umount: /home: target is busy
>         (In some cases useful info about processes that
>          use the device is found by lsof(8) or fuser(1).)
>
> (I'm logged in as root and it's home is /root, not in home.  /home has one
> user created during install and the lost+found dir.)
>
> What must occur to allow umount of /home?
>
>
> On Sun, Dec 28, 2014 at 3:28 PM, Jeff Jensen <jjensen at apache.org> wrote:
>
>> Hello,
>>
>> I just installed a fresh Fedora 21 without my RAID card in the machine.
>> All seemed well, so I installed the RAID card and booted.  The OS
>> automatically mounted it as /dev/md127 and the files I checked are good and
>> the state is clean.
>>
>> What is the correct procedure to unmount and eliminate the current /home
>> (created by the install) and mount it to /dev/md127 (which was the mount in
>> the prior machine)?
>>
>> I'm hesitant to try anything more than I have for fear of ruining
>> something!
>>
>> The two devices in question:
>> # df -h
>> Filesystem               Size  Used Avail Use% Mounted on
>> /dev/mapper/fedora-home   23G   49M   22G   1% /home
>> /dev/md127               2.7T  1.2T  1.5T  45%
>> /run/media/root/a60db566-0720-41a1-97d8-5afeddbbf802
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20141228/823b90ef/attachment.html>