On Thu, 24 Jan 2008 23:36:00 +0300, Al Boldi said:
data=ordered mode has proven reliable over the years, and it does this by
ordering filedata flushes before metadata flushes. But this sometimes
causes contention in the order of a 10x slowdown for certain apps, either
due to the misuse of
On Wed, 09 Jan 2008 07:40:12 +0300, Al Boldi said:
But why wouldn't it be possible to do this on the current fs infrastructure,
using just a smart fsck, working incrementally on some sub-dir?
If you have /home/usera, /home/userb, and /home/userc, the vast majority of
fs screw-ups can't be
On Thu, 06 Dec 2007 15:29:07 GMT, Pavel Machek said:
Why not use SELinux?
Because SELinux doesn't guarantee filename and its attribute.
The purpose of this filesystem is to ensure filename and its attribute
(e.g. /dev/null is guaranteed to be a character device file
with major=1
On Wed, 11 Jul 2007 18:44:21 EDT, Ric Wheeler said:
[EMAIL PROTECTED] wrote:
On Tue, 10 Jul 2007 14:39:41 EDT, Ric Wheeler said:
All of the high end arrays have non-volatile cache (read, on power loss,
it is a
promise that it will get all of your data out to permanent storage). You
On Tue, 10 Jul 2007 14:39:41 EDT, Ric Wheeler said:
All of the high end arrays have non-volatile cache (read, on power loss, it
is a
promise that it will get all of your data out to permanent storage). You
don't
need to ask this kind of array to drain the cache. In fact, it might just
On Fri, 01 Jun 2007 16:16:01 +0900, Tejun Heo said:
Don't those thingies usually have NV cache or backed by battery such
that ORDERED_DRAIN is enough?
Probably *most* do, but do you really want to bet the user's data on it?
The problem is that the interface between the host and a storage
On Mon, 28 May 2007 21:54:46 EDT, Kyle Moffett said:
Average users are not supposed to be writing security policy. To be
honest, even average-level system administrators should not be
writing security policy. It's OK for such sysadmins to tweak
existing policy to give access to
On Sat, 26 May 2007 22:10:34 EDT, Kyle Moffett said:
On May 26, 2007, at 19:08:56, Toshiharu Harada wrote:
(1) Object labeling has a assumption that labels are always
properly defined and maintained. This can not be easily achieved.
That's a circular argument, and a fairly trivial one
On Sun, 08 Apr 2007 21:16:59 PDT, [EMAIL PROTECTED] said:
I am not looking to defend Hans - he is likely to be in jail and no
longer a factor for a long time. Nor am I looking to make or support
claims for Reiser4.
Why not defend Hans? He is in jail on what appear to be trumped-up
On Sun, 08 Apr 2007 21:39:12 PDT, [EMAIL PROTECTED] said:
YOU GUYS WILL LAUGH ABOUT THIS:
I forgot the all the statistics that might support the sase for REISER4
inclusion.
Well, here it all is:
*plonk* - The sound of a sender address entering a procmail /dev/null filter.
Come back when
On Mon, 09 Apr 2007 18:41:08 +0200, Jan Engelhardt said:
On Apr 9 2007 12:55, Ronni Nielsen wrote:
oscar
And the award as Troll Of The Year goes to: johnrobertbanks.
/oscar
The year is not even over and you already picked your favorite -
who bribed you? :-)
The vast right-wing
On Sat, 07 Apr 2007 00:45:32 PDT, [EMAIL PROTECTED] said:
Use rpm-pkg to create a Red Hat RPM kernel package.
# make rpm-pkg
When built, the RPM package is put in
/usr/src/packages/RPMS/*your*architecture*
# cd /usr/src/packages/RPMS/x86_64
Install the package (you may have to
On Fri, 06 Apr 2007 19:47:36 PDT, [EMAIL PROTECTED] said:
On Fri, 6 Apr 2007 11:21:19 -0400, Jan Harkes [EMAIL PROTECTED]
With compression there is a pretty high probability that one corrupted
byte or disk block will result in loss of a considerably larger amount
of data.
Bad blocks
13 matches
Mail list logo
