tw_clin is the (binary only) command line tool for maintaining 3ware
controllers. All you can do with the web frontend can be done this
way, too.
Performance of the 3ware 8506 is pretty reasonable (I got a data rate
of ~ 80 MB/s with RAID 10 , 55-60 with RAID 1 ) and about the same
for reading an
On Jan 30, 2006, at 22:24, Greg KH wrote:
Oh, an example of it working:
# vol_id /dev/sda3
ID_FS_USAGE=filesystem
ID_FS_TYPE=ext3
ID_FS_VERSION=1.0
ID_FS_UUID=9d2efd53-6b5a-4f84-86cc-def71269b7ca
ID_FS_LABEL=
ID_FS_LABEL_SAFE=
# vol_
On Mon, Jan 30, 2006 at 05:42:45PM -0800, H. Peter Anvin wrote:
> What about non-DOS partitions?
Is something like libblkid suitable as a starting point of something
you can cut-down-to-size?
textdata bss dec hex filename
249782272 12 272626a7e /lib/libblkid.s
On Jan 30, 2006, at 21:01, Neil Brown wrote:
On Monday January 30, [EMAIL PROTECTED] wrote:
On Jan 30, 2006, at 20:10, Neil Brown wrote:
On Monday January 30, [EMAIL PROTECTED] wrote:
Any feeling how best to do that? My current thinking is to
export a "flags" entry in addition to the current
Greg KH wrote:
What are you looking for exactly? udev has a great helper program,
volume_id, that identifies any type of filesystem that Linux knows about
(it was based on the ext2 lib code, but smaller, and much more sane, and
works better.)
Would that help out here?
It might, but it's als
On Mon, Jan 30, 2006 at 07:21:33PM -0800, Greg KH wrote:
> On Mon, Jan 30, 2006 at 04:52:08PM -0800, H. Peter Anvin wrote:
> > I'm putting the final touches on kinit, which is the user-space
> > replacement (based on klibc) for the whole in-kernel root-mount complex.
> > Pretty much the one thi
On Mon, Jan 30, 2006 at 04:52:08PM -0800, H. Peter Anvin wrote:
> I'm putting the final touches on kinit, which is the user-space
> replacement (based on klibc) for the whole in-kernel root-mount complex.
> Pretty much the one thing remaining -- other than lots of testing --
> is to handle aut
Neil Brown wrote:
Mac partition tables doesn't currently support autodetect (as far as I
can tell). Let's keep it that way.
For now I guess I'll just take the code from init/do_mounts_md.c; we can
worry about ripping the RAID_AUTORUN code out of the kernel later.
-hpa
-
To unsubs
Neil Brown wrote:
Well, grepping through fs/partitions/*.c, the 'flags' thing is set by
efi.c, msdos.c sgi.c sun.c
Of these, efi compares something against PARTITION_LINUX_RAID_GUID,
and msdos.c, sgi.c and sun. compare something against
LINUX_RAID_PARTITION.
The former would look like
e6d6d
On Monday January 30, [EMAIL PROTECTED] wrote:
> On Jan 30, 2006, at 20:10, Neil Brown wrote:
> > On Monday January 30, [EMAIL PROTECTED] wrote:
> >> Any feeling how best to do that? My current thinking is to export
> >> a "flags" entry in addition to the current ones, presumably based
> >> on
On Monday January 30, [EMAIL PROTECTED] wrote:
> Neil Brown wrote:
> > On Monday January 30, [EMAIL PROTECTED] wrote:
> >
> >>Any feeling how best to do that? My current thinking is to export a
> >>"flags" entry in addition to the current ones, presumably based on
> >>"struct parsed_partitions-
Kyle Moffett wrote:
Well, for an MSDOS partition table, you would look for '253', for a Mac
partition table you could look for something like 'Linux_RAID' or
similar (just arbitrarily define some name beginning with the Linux_
prefix), etc. This means that the partition table type would n
On Jan 30, 2006, at 20:10, Neil Brown wrote:
On Monday January 30, [EMAIL PROTECTED] wrote:
Any feeling how best to do that? My current thinking is to export
a "flags" entry in addition to the current ones, presumably based
on "struct parsed_partitions->parts[].flags" fs/partitions/
check.h
Neil Brown wrote:
On Monday January 30, [EMAIL PROTECTED] wrote:
Any feeling how best to do that? My current thinking is to export a
"flags" entry in addition to the current ones, presumably based on
"struct parsed_partitions->parts[].flags" (fs/partitions/check.h), which
seems to be what ca
On Monday January 30, [EMAIL PROTECTED] wrote:
>
> Any feeling how best to do that? My current thinking is to export a
> "flags" entry in addition to the current ones, presumably based on
> "struct parsed_partitions->parts[].flags" (fs/partitions/check.h), which
> seems to be what causes md_au
Dear potential speaker:
Please, read carefully and respond with "SUBSCRIBE." We will be informing you
about our future conferences 4 to 6 times per year, only if you subscribe now!
If you do not respond to this email, we will NEVER send you an email invitation
again.
The list of our 2006 conf
It is possible to run SMART commands through to individual drives on
3ware cards, even if you set the drives up as a hardware RAID array
(making them non-addressable otherwise). I'd read up on 'smartmontools'
(the linux SMART protocol implementation) and get ready to set up smartd
to scan the driv
On Monday January 30, [EMAIL PROTECTED] wrote:
>
> Question to the linux-raid folks: Does md support disks on different
> SCSI host adapters to be in the same RAID set?
>
md doesn't notice and doesn't care what the underlying devices are.
It just sees Linux block devices, and sends read/write r
Francois Barre wrote:
This is a cross-post (sorry for that), but I don't know where it comes from yet.
Alas we get similar reports about software RAID over SBP-2 now and then
on linux1394-devel or -user. I very much suspect sbp2 to be the culprit.
One person reported different results with d
19 matches
Mail list logo
