![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Reasons to Reboot Linux
Jan. 27th, 2009 04:10 pmNow, it may just be that I have no idea of what commands to issue to correct these problems that I've been correcting by rebooting my Linux box, but I haven't had much success trying to google for other solutions, so any information folks might have would help.
1) I have a 1TB disk with an XFS filesystem that, until recently, had a 500GB file on it. I deleted the file to make room for more stuff, and started copying onto the drive, only to be told it was full. A quick check got me very confused as df claimed the drive was full, while du over the drive said it was half-full. I couldn't unmount the drive because it said it was 'busy'. I couldn't figure out what process (if any) was holding the drive open. Certainy none that I could figure out. I'm guessing that something had a handle on the now-missing 500GB file and it wasn't really gone until that handle was released, but I could find no way to sort that out short of rebooting.
2) I've been doing a LOT of data transfers between separate drives lately. As such it really matters to me if that transfer happens at 1.2MB/s or 35MB/s. For some reason, the exact same setup with the exact same commands will sometimes give me one, sometimes the other. Again, I usually solve this by rebooting. (... although I'm beginning to wonder if its because on the second try I usually mount manually, where on the first I just click on the mount icon. I wonder if the mount parameters are different enough to cause the problem...)
1) I have a 1TB disk with an XFS filesystem that, until recently, had a 500GB file on it. I deleted the file to make room for more stuff, and started copying onto the drive, only to be told it was full. A quick check got me very confused as df claimed the drive was full, while du over the drive said it was half-full. I couldn't unmount the drive because it said it was 'busy'. I couldn't figure out what process (if any) was holding the drive open. Certainy none that I could figure out. I'm guessing that something had a handle on the now-missing 500GB file and it wasn't really gone until that handle was released, but I could find no way to sort that out short of rebooting.
2) I've been doing a LOT of data transfers between separate drives lately. As such it really matters to me if that transfer happens at 1.2MB/s or 35MB/s. For some reason, the exact same setup with the exact same commands will sometimes give me one, sometimes the other. Again, I usually solve this by rebooting. (... although I'm beginning to wonder if its because on the second try I usually mount manually, where on the first I just click on the mount icon. I wonder if the mount parameters are different enough to cause the problem...)
