Re: flush?
On Jan 6 Mark wrote: Nope, sync won't do it. ;) I can sync all I want, but df (and dd, effectively, by adding the deleted size to its image) keeps reporting the added size (which is considerable: about 4 G extra) to the partition, and only falls back to the true value after a while. Besides, being in disk-cache would not itself adversely affect dd. This could be the `softupdates' effect. -andrew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: flush?
sync? `Anti` On Sun, 5 Jan 2003 22:07:19 +0100 Mark [EMAIL PROTECTED] wrote: When I use dump to make a backup, I noticed that a very large file (several G), which had just been moved off the partition (several seconds before), seems to have been backup-ed by dump after all. Or, I should say, its size seems to be added to the dump-file, making my backup of that partition several G larger than it should be. This must be some sort of caching problem, as I already saw this once before, on using df, where df, for a while thereafter, still shows the size of a partition occupied after deleting a large file, only to drop back to its normal indication a few seconds later. Or it could be that dump, while the file has already been deleted, just grows extra large because of all those blocks that have been used. :( Is there a way I can flush this cache, so dump will only use files that actually still exist? Thanks. - Mark System Administrator Asarian-host.org --- If you were supposed to understand it, we wouldn't call it code. - FedEx To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: flush?
Nope, sync won't do it. ;) I can sync all I want, but df (and dd, effectively, by adding the deleted size to its image) keeps reporting the added size (which is considerable: about 4 G extra) to the partition, and only falls back to the true value after a while. Besides, being in disk-cache would not itself adversely affect dd. I managed to solve it now by just adding a 5 min sleep period in-between dumps, but, obviously, that is a crappy solution. - Mark System Administrator Asarian-host.org --- If you were supposed to understand it, we wouldn't call it code. - FedEx - Original Message - From: Anti [EMAIL PROTECTED] To: Mark [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, January 06, 2003 4:12 AM Subject: Re: flush? sync? `Anti` On Sun, 5 Jan 2003 22:07:19 +0100 Mark [EMAIL PROTECTED] wrote: When I use dump to make a backup, I noticed that a very large file (several G), which had just been moved off the partition (several seconds before), seems to have been backup-ed by dump after all. Or, I should say, its size seems to be added to the dump-file, making my backup of that partition several G larger than it should be. This must be some sort of caching problem, as I already saw this once before, on using df, where df, for a while thereafter, still shows the size of a partition occupied after deleting a large file, only to drop back to its normal indication a few seconds later. Or it could be that dump, while the file has already been deleted, just grows extra large because of all those blocks that have been used. :( Is there a way I can flush this cache, so dump will only use files that actually still exist? Thanks. - Mark To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
