-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Mindaugas,
On 07/23/2012 12:55 AM, Mindaugas Rasiukevicius wrote:
Hello Lars,
Lars Heidieker l...@heidieker.de wrote:
slight improvement on kmem(9):
splitting the lookup table into two parts - this reduces the size
of the lookup table -
You can put a wedge on the disk
That seems to work. At least with manually created (dkctl addwedge) wedges.
or put the raid on the raw disk itself.
That doesn't work. It truncates the component capacity to the truncated
value in the disklabel.
I even tried to create (raidctl -C) the set with
Can I somehow pin down which dk? gets assigned to which GPT partition?
In a disklabel world, I have components sd2a..sd6a making raid1.
I then have raid1a mounted on /export/home and raid1e on /export/mail.
In a GPT/wedge word, I have dk0..dk4 (on sd2..sd6) making raid1.
I then have dk5 and dk6
On Mon, Jul 23, 2012 at 04:17:21PM +0200, Edgar Fuß wrote:
Can I somehow pin down which dk? gets assigned to which GPT partition?
You can mount them by name. I have (on my non-GPT root disk):
NAME=sb2k5Root/a/ ffs rw,log 1 1
NAME=sb2k5Root/bnoneswap
Martin Husemann mar...@duskware.de writes:
On Mon, Jul 23, 2012 at 04:17:21PM +0200, Edgar Fuß wrote:
Can I somehow pin down which dk? gets assigned to which GPT partition?
You can mount them by name. I have (on my non-GPT root disk):
NAME=sb2k5Root/a/ ffs rw,log
On Mon, Jul 23, 2012 at 10:24:38AM -0400, Greg Troxel wrote:
Thanks - I had no idea. This seems to be missing from the
documentation. Is it new?
You can find it in fstab(5), but I guess a few hints in wedge related
man pages would not hurt. It is not very new, -6 should have it as well.
You can find it in fstab(5)
Not in 6.0_BETA.
It is not very new, -6 should have it as well.
Does it? the only special handling of fs_spec I could find in
sbin/mount/mount.c was ``from_mount'', whatever that is.
In article 20120723141721.gj4...@trav.math.uni-bonn.de,
Edgar Fuß e...@math.uni-bonn.de wrote:
Can I somehow pin down which dk? gets assigned to which GPT partition?
In a disklabel world, I have components sd2a..sd6a making raid1.
I then have raid1a mounted on /export/home and raid1e on
Use NAME=guid or NAME=underlying-device-name instead of /dev/dkX for the
fs_spec field.
Yes, but someone would have to pull-up that to 6.0.
6.0 has src/bin/mount/mount.c 1.94 and NAME= was introduced in 1.95.
or put the raid on the raw disk itself.
That doesn't work. It truncates the component capacity to the
truncated value in the disklabel.
That could easily just be a code bug.
Back some years ago, I had occasion to (for work) set up a RAID of
something like six or seven TB. The individual
That could easily just be a code bug.
Back some years ago, I had occasion to (for work) set up a RAID of
something like six or seven TB. The individual drives were well under
the 2T limit, but even so I had some 32-bit bugs to fix. It's possible
there's another one in the code path that
g...@ir.bbn.com (Greg Troxel) writes:
NAME=3Dsb2k5Root/a/ ffs rw,log 1 1
NAME=3Dsb2k5Root/bnoneswapsw,dp0 0
in /etc/fstab. With gpt you can label the partitions with arbitrary names
(instead of the disklabel volume name/partition that I
It probably won't help you with raidframe.
It would indeed help in my case. In case sd6 has gone missing, so dk4 is on the
RAID and not on sd6, it would prevent the wrong filesystem being mounted for
dk5.
e...@math.uni-bonn.de (=?iso-8859-1?Q?Edgar_Fu=DF?=) writes:
It probably won't help you with raidframe.
It would indeed help in my case. In case sd6 has gone missing, so dk4 is on
the RAID and not on sd6, it would prevent the wrong filesystem being mounted
for dk5.
I was refering to the
Back some years ago, I had occasion to (for work) set up a RAID of
something like six or seven TB. The individual drives were well
under the 2T limit, but even so I had some 32-bit bugs to fix.
support for 2TB raidframe was not implemented until this comment:
date: 2010/11/01 02:35:25;
It's possible there were other fixes required elsewhere in the tree,
but I don't think so.
ah, i see. there are a few other changes that you might want to
pick up, though i see that the majority of my changes were to make
it handle 2TB components, though the component label should also
have
In article juk971$qpi$1...@serpens.de,
Michael van Elst mlel...@serpens.de wrote:
e...@math.uni-bonn.de (=?iso-8859-1?Q?Edgar_Fu=DF?=) writes:
It probably won't help you with raidframe.
It would indeed help in my case. In case sd6 has gone missing, so dk4
is on the RAID and not on sd6, it would
chris...@astron.com (Christos Zoulas) writes:
In article juk971$qpi$1...@serpens.de,
Michael van Elst mlel...@serpens.de wrote:
e...@math.uni-bonn.de (=?iso-8859-1?Q?Edgar_Fu=DF?=) writes:
It probably won't help you with raidframe.
It would indeed help in my case. In case sd6 has gone missing,
18 matches
Mail list logo
