hi,
Am Mittwoch, den 27.04.2011, 20:23 -0700 schrieb Jeremy Chadwick:
> I don't mean to sound critical, but why do you guys do this?
two answers:
1.) Think of: It could happen, instead of it shouldn't happen :-)
2.) Adding a new JBOD on the fly, without reboot the whole machine, what
I've done
On Wed, Apr 27, 2011 at 08:07:34PM -0700, Rumen Telbizov wrote:
> I confirm I experience the same behavior with just a SAS expander not
> via SAS switch. I've got no way to get my block device back but
> reboot.
I don't mean to sound critical, but why do you guys do this? The reason
I ask: on ac
Hello Denny, everyone,
I confirm I experience the same behavior with just a SAS expander not via
SAS switch.
I've got no way to get my block device back but reboot. Also identify
function doesn't work
from the OS (no problem via the card BIOS). Don't remember having any luck
with sg3_util
package
Michael Proto wrote:
> What I ultimately decided to do was use fdisk in interactive mode to
> manually align 2 4k-boundary MBR partitions
Correct me if I'm wrong but from my point of view there is no need to
fall back to MBR partitions. GPT partitions should be at least as
robust as MBR partition
On Wed, Apr 27, 2011 at 6:30 PM, Freddie Cash wrote:
> On Wed, Apr 27, 2011 at 3:15 PM, Clifton Royston wrote:
>> I don't know; it looks correct to me, but I may be missing something
>> as I don't currently use gpart.
>
> gmirror (well, really, any GEOM) doesn't play well with GPT due to the
> w
On Wed, Apr 27, 2011 at 3:15 PM, Clifton Royston wrote:
> I don't know; it looks correct to me, but I may be missing something
> as I don't currently use gpart.
gmirror (well, really, any GEOM) doesn't play well with GPT due to the
way they store their metadata.
gmirror doesn't touch the start
On Wed, Apr 27, 2011 at 07:35:22PM +, Helmut Schneider wrote:
> Michael Proto wrote:
...
> > gmirror label -v -n -b round-robin gm0p1 /dev/ad4p1
> > newfs -U -b 32768 -f 4096 -S 4096 /dev/mirror/gm0p1
> >
> > gmirror label -v -n -b round-robin gm0p2 /dev/ad4p2
> > newfs -U -b 32768 -f 4096 -S
Helmut 'Ingrid' Schneider wrote:
> running 8.2-RELEASE-p1 within VMWare ESXi 4.1-u1 I want to use raw
> devices as hard disks. I create the devices using this link:
>
> http://www.mattiasholm.com/node/33
>
> I tried 3 different hard drives (Seagate 2x80GB and 1x400GB SATA2)
> which are fine on a
On Wed, Apr 27, 2011 at 4:43 PM, Helmut Schneider wrote:
> Michael Proto wrote:
>
>> On Wed, Apr 27, 2011 at 3:35 PM, Helmut Schneider
>> wrote:
>> > Michael Proto wrote:
>> >> Am I using the correct process to create this array?
>> >
>> > No. While this works with MBR it fails with GPT as GPT an
Michael Proto wrote:
> On Wed, Apr 27, 2011 at 3:35 PM, Helmut Schneider
> wrote:
> > Michael Proto wrote:
> >> Am I using the correct process to create this array?
> >
> > No. While this works with MBR it fails with GPT as GPT and GEOM both
> > want to use the last sector of the disk.
> >
> >
On Wed, Apr 27, 2011 at 3:35 PM, Helmut Schneider wrote:
> Michael Proto wrote:
>> Am I using the correct process to create this array?
>
> No. While this works with MBR it fails with GPT as GPT and GEOM both
> want to use the last sector of the disk.
>
> First create the mirror and after that gpa
Michael Proto wrote:
> I'm migrating away from my old pseudo-RAID partitions to GEOM gmirror
> and I have some questions on the right way to accomplish this. I've
> got two new 1TB disks that I'm setting up for the new mirror, and
> unfortunately they're Western Digital drives with 4k sectors that
I'm migrating away from my old pseudo-RAID partitions to GEOM gmirror
and I have some questions on the right way to accomplish this. I've
got two new 1TB disks that I'm setting up for the new mirror, and
unfortunately they're Western Digital drives with 4k sectors that
report themselves as 512b.
H
Hi,
running 8.2-RELEASE-p1 within VMWare ESXi 4.1-u1 I want to use raw
devices as hard disks. I create the devices using this link:
http://www.mattiasholm.com/node/33
I tried 3 different hard drives (Seagate 2x80GB and 1x400GB SATA2)
which are fine on a physical machine. I also ran Seatool many
On 27.04.2011 16:39, Denny Schierz wrote:
Am Mittwoch, den 27.04.2011, 05:57 -0700 schrieb Jeremy Chadwick:
camcontrol reset 0
0:22:0 is available, 0:46:0 not:
root@iscsihead-m:~# camcontrol reset 0:22:0
Reset of 0:22:0 was successful
root@iscsihead-m:~# camcontrol reset 0:46:0
camcontrol: c
On Wed, 27 Apr 2011 14:05:11 +0200 Denny Schierz wrote:
DS> hi,
DS> Am Dienstag, den 29.03.2011, 23:36 +0300 schrieb Mikolaj Golub:
>>
>> 2) There are complaints from watchdog.
DS> what happens, if the watchdog isn't available and one or both nodes are
DS> rebooting or something else?
hi,
Am Mittwoch, den 27.04.2011, 05:57 -0700 schrieb Jeremy Chadwick:
> camcontrol reset 0
0:22:0 is available, 0:46:0 not:
root@iscsihead-m:~# camcontrol reset 0:22:0
Reset of 0:22:0 was successful
root@iscsihead-m:~# camcontrol reset 0:46:0
camcontrol: cam_open_btl: no passthrough device foun
On Wed, Apr 27, 2011 at 02:20:34PM +0200, Denny Schierz wrote:
> hi,
>
> if I remove the SAS cable from the JBOD (connected through a SAS
> switch), all disks disappears, that's fine and expected, but if I
> reconnect the cable, the disks are not added anymore.
> I've red to use "camcontrol rescan
hi,
Am Mittwoch, den 27.04.2011, 14:20 +0200 schrieb Denny Schierz:
> I've red to use "camcontrol rescan all", but nothing happens. I don't
> get my /dev/da0-47 devices anymore and have to reboot the whole machine.
small update: I've tested it again and only some disks appear again, but
not all.
hi,
if I remove the SAS cable from the JBOD (connected through a SAS
switch), all disks disappears, that's fine and expected, but if I
reconnect the cable, the disks are not added anymore.
I've red to use "camcontrol rescan all", but nothing happens. I don't
get my /dev/da0-47 devices anymore and
hi,
Am Dienstag, den 29.03.2011, 23:36 +0300 schrieb Mikolaj Golub:
>
> 2) There are complaints from watchdog.
what happens, if the watchdog isn't available and one or both nodes are
rebooting or something else?
the other thing what could happen: the connection between the host and
the SAS swi
FreeBSD Quarterly Status Report January-March, 2011
Introduction
This report covers FreeBSD-related projects between January and March
2011. It is the first of the four reports planned for 2011. During this
quarter, the work was focused on releasing the new minor versions of
FreeBSD,
22 matches
Mail list logo
