From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 3475] New: Calling sync on large filesystems when not always necessary
Date: Fri, 11 Mar 2011 16:20:22 +0000 (UTC) [thread overview]
Message-ID: <bug-3475-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=3475
Summary: Calling sync on large filesystems when not always
necessary
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: orionrobots at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
When using build root to cross compile for other devices, especially when doing
many builds (multiple targets), on a CI system with 10s of gigs of ram and many
intermediate targets, then sync is not really desirable here.
The makedevs step makes a call to /bin/sync.
I am suggesting a "--nosync" be introduced so buildroot will not sync the
drives then? While of course preserving existing behaviour for the majority
that don't find any problems.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2011-03-11 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 16:20 bugzilla at busybox.net [this message]
2011-03-11 16:22 ` [Buildroot] [Bug 3475] Calling sync on large filesystems when not always necessary bugzilla at busybox.net
2011-03-11 23:18 ` bugzilla at busybox.net
2011-03-12 21:29 ` bugzilla at busybox.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-3475-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.