On Wed, Feb 06, 2008 at 04:45:39PM +0100, Keld Jørn Simonsen wrote:
On Wed, Feb 06, 2008 at 10:05:58AM +0100, Luca Berra wrote:
On Sat, Feb 02, 2008 at 08:41:31PM +0100, Keld Jørn Simonsen wrote:
Make each of the disks bootable by lilo:
lilo -b /dev/sda /etc/lilo.conf1
lilo -b /dev/sdb
Dear Nail,
in message [EMAIL PROTECTED] you wrote:
quote
The second improvement is to remove a memory copy that is internal to the MD
driver. The MD
driver stages strip data ready to be written next to the I/O controller in a
page size pre-
allocated buffer. It is possible to bypass
On Thu, Feb 07, 2008 at 09:05:04AM +0100, Luca Berra wrote:
On Wed, Feb 06, 2008 at 04:45:39PM +0100, Keld Jørn Simonsen wrote:
On Wed, Feb 06, 2008 at 10:05:58AM +0100, Luca Berra wrote:
On Sat, Feb 02, 2008 at 08:41:31PM +0100, Keld Jørn Simonsen wrote:
Make each of the disks bootable by
On Thu, Feb 07, 2008 at 06:40:12AM +0100, Iustin Pop wrote:
On Thu, Feb 07, 2008 at 01:31:16AM +0100, Keld Jørn Simonsen wrote:
Anyway, why does a SATA-II drive not deliver something like 300 MB/s?
Wait, are you talking about a *single* drive?
Yes, I was talking about a single drive.
In
Hello,
On platforms with PAGE_SIZE set to rather big values (e.g. 256KB) the
amount of memory necessary for for the stripe cache may be significant,
so we can't rely on the hard-coded value of initial max_nr_stripes
(this may cause invoking OOM-killer for terminating RAID creation process).
Hi
I am trying to get some order to linux raid info.
I think we should have a faq and a howto for the linux-raid list.
The list description at
http://vger.kernel.org/vger-lists.html#linux-raid
does list af FAQ, http://www.linuxdoc.org/FAQ/
I cannot read it just now - the server
On Thursday February 7, [EMAIL PROTECTED] wrote:
As I understand it, there are 2 valid algoritms for writing in raid5.
1. calculate the parity data by XOR'ing all data of the relevant data
chunks.
2. calculate the parity data by kind of XOR-subtracting the old data to
be changed, and then
On Tuesday 05 February 2008 03:02:00 Neil Brown wrote:
On Monday February 4, [EMAIL PROTECTED] wrote:
Seems the other topic wasn't quite clear...
not necessarily. sometimes it helps to repeat your question. there
is a lot of noise on the internet and somethings important things get
On Thursday February 7, [EMAIL PROTECTED] wrote:
On Tuesday 05 February 2008 03:02:00 Neil Brown wrote:
On Monday February 4, [EMAIL PROTECTED] wrote:
Seems the other topic wasn't quite clear...
not necessarily. sometimes it helps to repeat your question. there
is a lot of noise on
Andreas-Sokov wrote:
Hello, Neil.
.
Possible you have bad memory, or a bad CPU, or you are overclocking
the CPU, or it is getting hot, or something.
As seems to me all my problems has been started after i have started update
MDADM.
This is server worked normaly (but only not
Moshe Yudkowsky wrote:
maximilian attems wrote:
error 15 is an *grub* error.
grub is known for it's dislike of xfs, so with this whole setup use ext3
rerun grub-install and you should be fine.
I should mention that something *did* change. When attempting to use
XFS, grub would give me a
Marcin Krol wrote:
Thursday 07 February 2008 03:36:31 Neil Brown napisał(a):
8 0 390711384 sda
8 1 390708801 sda1
816 390711384 sdb
817 390708801 sdb1
832 390711384 sdc
833 390708801 sdc1
848 390710327 sdd
849 390708801 sdd1
Bill Davidsen wrote:
Moshe Yudkowsky wrote:
maximilian attems wrote:
error 15 is an *grub* error.
grub is known for it's dislike of xfs, so with this whole setup use
ext3
rerun grub-install and you should be fine.
I should mention that something *did* change. When attempting to use
XFS,
As I understand it, there are 2 valid algoritms for writing in raid5.
1. calculate the parity data by XOR'ing all data of the relevant data
chunks.
2. calculate the parity data by kind of XOR-subtracting the old data to
be changed, and then XOR-adding the new data. (XOR-subtract and XOR-add
is
On Jan 29 2008 18:08, Bill Davidsen wrote:
IIRC there was a discussion a while back on renaming mdadm options
(google Time to deprecate old RAID formats?) and the superblocks
to emphasise the location and data structure. Would it be good to
introduce the new names at the same time as
On Fri, Feb 08, 2008 at 07:25:31AM +1100, Neil Brown wrote:
On Thursday February 7, [EMAIL PROTECTED] wrote:
As I understand it, there are 2 valid algoritms for writing in raid5.
1. calculate the parity data by XOR'ing all data of the relevant data
chunks.
2. calculate the parity
On Friday February 8, [EMAIL PROTECTED] wrote:
On Fri, Feb 08, 2008 at 07:25:31AM +1100, Neil Brown wrote:
On Thursday February 7, [EMAIL PROTECTED] wrote:
So I hereby give the idea for inspiration to kernel hackers.
and I hereby invite you to read the code ;-)
I did some reading.
17 matches
Mail list logo
