Hello,
> > Pawel Jakub Dawidek wrote:
> > > You should be safe as long as the order of slices you give here is the
> > > same as it was when device was initially labeled.
I have follow this procedure and it worked for me:
select "6. Escape to loader prompt"
OK unload
OK disable-module geom_r
"José M. Fandiño" wrote:
>
> Pawel Jakub Dawidek wrote:
> > +> Unfortunately, the metadata structure of my data partition (a geom raid3
> > +> array with tree components ) seems to be corrupted by this hard lock,
> > +> the following m
Pawel Jakub Dawidek wrote:
> +> Unfortunately, the metadata structure of my data partition (a geom raid3
> +> array with tree components ) seems to be corrupted by this hard lock,
> +> the following message is scrolled constantly on the screen:
> +>
> +> GEOM_RAID3: Device datos created (id=3217
Hello list,
Last night one disk of my desktop machine dead causing a hard lock of the
computer. It was a component of a mirror volume so it wasn't as serious as
it initially looked.
Unfortunately, the metadata structure of my data partition (a geom raid3
array with tree components ) see
Hello,
Recently I have upgraded a FBSD laptop from 5-STABLE to 6.0RC1,
all seems works except the usb-rs232 adapter which is detected
by the umct and ucom modules as:
ucom0: USB-RS232 Interface Converter USB Ver1.2 Device, rev 1.10/1.03,
addr 3
however no /dev entry is created for this adapte
Accidentally I set this variable to 0 and it causes a hard lock (FreeBSD
5.4-RELEASE-p2)
could someone check if this reproducible in their test machines so I can
open a pr?
/---/
Geom name: datos
State: COMPLETE
Components: 3
Flags: ROUND-ROBIN
GenID: 0
SyncID: 3
ID: 3217021940
P
Kris Kennaway wrote:
>
> On Mon, Feb 07, 2005 at 11:15:52AM +0100, Jos? M. Fandi?o wrote:
> > "Jos? M. Fandi?o" wrote:
> > >
> > > Chris wrote:
> > > >
> > > > Have tested on 3 boxes.
> > >
> > > yes, it's the intended operation and If I don't see it I don't
> > > believe it but it happens. I ever
"José M. Fandiño" wrote:
>
> Chris wrote:
> >
> > Have tested on 3 boxes.
>
> yes, it's the intended operation and If I don't see it I don't
> believe it but it happens. I ever thought it would be possible.
Finally, I found the culprit:
kets received, 0% packet loss
> round-trip min/avg/max/stddev = 0.024/0.030/0.048/0.005 ms
>
> 5.3-Release-P5
>
> --- 127.0.0.1 ping statistics ---
> 60 packets transmitted, 60 packets received, 0% packet loss
> round-trip min/avg/max/stddev = 0.057/0.089/0.167/0.017 ms
>
Hello,
It sounds weird but tcp/ip traffic directed to _local_ interfaces,
and only _local_ interfaces, always cause 50% of packets lost. Of
course there isn't packet filters activated.
I'm running -stable (the last update was this past weekend)
There is another report like this:
http://www.Fre
10 matches
Mail list logo
