bugzilla-daemon@dp3.samba.org
2006-Jan-04 08:35 UTC
DO NOT REPLY [Bug 3371] New: no way to limit disk IO bandwidth
https://bugzilla.samba.org/show_bug.cgi?id=3371 Summary: no way to limit disk IO bandwidth Product: rsync Version: 2.6.6 Platform: x86 URL: https://bugzilla.samba.org/show_bug.cgi?id=2800 OS/Version: Linux Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: truxton@truxton.com QAContact: rsync-qa@samba.org Hi, My problem is the opposite of bug #2800. I have a large filesystem that I want to keep in sync, but I dont want to thrash the disk each time I start rsync. I dont mind if the checksum stage takes a long time, I just want to be gentle with disk IO. Can a --disk-bwlimit option be added? Thanks, -Truxton -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.
samba-bugs at samba.org
2009-Aug-07 09:08 UTC
DO NOT REPLY [Bug 3371] no way to limit disk IO bandwidth
https://bugzilla.samba.org/show_bug.cgi?id=3371 devzero at web.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |devzero at web.de ------- Comment #1 from devzero at web.de 2009-08-07 04:08 CST ------- this could perhaps be handled as duplicate of https://bugzilla.samba.org/show_bug.cgi?id=3491 seems, i can`t mark it as a duplicate. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.
Apparently Analagous Threads
- DO NOT REPLY [Bug 7120] New: Variable bandwidth limit .. bwlimit
- DO NOT REPLY [Bug 7349] New: Add --limit-time=<seconds> and --fit-time=[seconds] options
- DO NOT REPLY [Bug 3491] New: throttle disk IO during filelist/directory parsing
- DO NOT REPLY [Bug 7425] New: --files-from= broken when run from crontab
- [Bug 8375] New: rsync with bandwidth limit sometimes expend extra time