Linux - KernelThis forum is for all discussion relating to the Linux kernel.

Notices

Welcome to LinuxQuestions.org, a friendly and active Linux Community.

You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

For a long time I've used rsync to backup my documents directory to a usb stick without any issues. Since upgrading the umount command takes a very long time to umount the usb drive. This is what I do -

the Size, Used, Avail and Use% which df is reporting during the umount just so happens to be exactly the same numbers as df reports for /dev/root. So something's got confused somewhere.

Now if the system, on the umount, now sees a drive of 37G whereas it should see a drive of only 3.8G this could explain why it takes a long time to umount. However, there is minimal disk activity on /dev/root and a lot of activity on /dev/sdc1. Eventually it is the correct partition that is unmounted.

As this problem seems to be so bizarre and I've not managed to find a similar posting elsewhere I might elect to do a fresh install and see what happens.

I also recognized a change in my USB-device behaviour. If I copy a huge amount of data to a USB-stick, and the data is not to huge to go to the cache first, then the data is copied into the cache and the copy command returns. The real copy process is backgrounded to another thread. So if you immediatly unmount after copying the mount command waits until the data is copied.
I think this is the same thing that you have recognized on your system.