[opensuse-buildservice] JFYI: we are using ext4 now
JFYI, by default all build instances are using ext4 instead of ext3 file system now. We did this switch for all distros to support SSD disks better. There is a little chance that this might influence build results, so it should not. However, please report if you spot a problem. We may do the switch only for selected distributions in that case. thanks adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Friday 2012-10-05 10:00, Adrian Schröter wrote:
JFYI, by default all build instances are using ext4 instead of ext3 file system now.
We did this switch for all distros to support SSD disks better.
How about using XFS? ext falls over in high parallelism - and that certainly exists on all the per-host workers doing build setup/teardown in the BSrv. http://www.youtube.com/watch?v=FegjLbCnoBw -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Fri, Oct 5, 2012 at 5:00 AM, Adrian Schröter
JFYI, by default all build instances are using ext4 instead of ext3 file system now.
We did this switch for all distros to support SSD disks better.
There is a little chance that this might influence build results, so it should not.
However, please report if you spot a problem. We may do the switch only for selected distributions in that case.
I imagine you've seen this[0]? [0] http://www.phoronix.com/scan.php?page=news_item&px=MTIxNDQ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
I imagine you saw this[0] too? Meaning that most (99.99%) of our users
and systems ARE NOT AFFECTED.
[0] http://lwn.net/Articles/521701/
On Thu, Nov 1, 2012 at 5:30 AM, Claudio Freire
On Fri, Oct 5, 2012 at 5:00 AM, Adrian Schröter
wrote: JFYI, by default all build instances are using ext4 instead of ext3 file system now.
We did this switch for all distros to support SSD disks better.
There is a little chance that this might influence build results, so it should not.
However, please report if you spot a problem. We may do the switch only for selected distributions in that case.
I imagine you've seen this[0]?
[0] http://www.phoronix.com/scan.php?page=news_item&px=MTIxNDQ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Thursday 01 November 2012, Jan Engelhardt wrote:
On Friday 2012-10-05 10:00, Adrian Schröter wrote:
JFYI, by default all build instances are using ext4 instead of ext3 file system now.
We did this switch for all distros to support SSD disks better.
How about using XFS? ext falls over in high parallelism - and that certainly exists on all the per-host workers doing build setup/teardown in the BSrv.
XFS is terribly slow with many/small files, specially when deleting. So IMO this can't be a good choice for mostly doing make and rpm -i. cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Thu, Nov 1, 2012 at 5:34 AM, Boris Manojlovic
I imagine you saw this[0] too? Meaning that most (99.99%) of our users and systems ARE NOT AFFECTED.
I didn't mean users. I meant OBS. Not sure, but OBS might be mounting and unmounting repeatedly, which is what causes corruption. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
My understanding is that the corruption only happens when journal_checksum is turned on (not the default) *and* the filesystem is unmounted/mounted before the journal wraps (highly unlikely in a build scenario). -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
El 01/11/12 05:34, Boris Manojlovic escribió:
I imagine you've seen this[0]?
[0] http://www.phoronix.com/scan.php?page=news_item&px=MTIxNDQ
Filesystem corruption does not matter in the OBS virtual machines , if something fails the build is retried. There is no journaling or disk cache safety in place, it has been disable on purpose for the sake of speed. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Thu, Nov 1, 2012 at 11:53 AM, Cristian Rodríguez
El 01/11/12 05:34, Boris Manojlovic escribió:
I imagine you've seen this[0]?
[0] http://www.phoronix.com/scan.php?page=news_item&px=MTIxNDQ
Filesystem corruption does not matter in the OBS virtual machines , if something fails the build is retried.
The presence of corruption does not imply a failed build. -- Jon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Claudio Freire
On Thu, Nov 1, 2012 at 5:34 AM, Boris Manojlovic
wrote: I imagine you saw this[0] too? Meaning that most (99.99%) of our users and systems ARE NOT AFFECTED.
I didn't mean users. I meant OBS.
Not sure, but OBS might be mounting and unmounting repeatedly, which is what causes corruption.
I assume obs uses disposible VMs. Ie. Instantiate a virgin VM, use it once and throw it away. Snapshot technology can make that pretty efficient. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Freitag, 2. November 2012, 23:24:56 schrieb Greg Freemyer:
Claudio Freire
wrote: On Thu, Nov 1, 2012 at 5:34 AM, Boris Manojlovic
wrote: I imagine you saw this[0] too? Meaning that most (99.99%) of our users and systems ARE NOT AFFECTED.
I didn't mean users. I meant OBS.
Not sure, but OBS might be mounting and unmounting repeatedly, which is what causes corruption.
I assume obs uses disposible VMs. Ie. Instantiate a virgin VM, use it once and throw it away.
Snapshot technology can make that pretty efficient.
We never do mount a partition used for build, because the risk that you can exploit the filesystem code of the kernel is just to high. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Donnerstag, 1. November 2012, 03:52:14 schrieb Jan Engelhardt:
On Friday 2012-10-05 10:00, Adrian Schröter wrote:
JFYI, by default all build instances are using ext4 instead of ext3 file system now.
We did this switch for all distros to support SSD disks better.
How about using XFS? ext falls over in high parallelism - and that certainly exists on all the per-host workers doing build setup/teardown in the BSrv.
XFS has no support for SSD's.
http://www.youtube.com/watch?v=FegjLbCnoBw -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (8)
-
Adrian Schröter
-
Boris Manojlovic
-
Claudio Freire
-
Cristian Rodríguez
-
Greg Freemyer
-
Jan Engelhardt
-
Jon Nelson
-
Ruediger Meier