Hi,
since GEOM so a nicely layered framework (and I didnt want to loose my MBR)
I tried to setup a graid3 using using da1s1a... instead of da1...
getting the following negative results:
(not only trying to use da1/da1s1 for parity,
it trashes the disklabel on da1s1 too)
...
(totum)(root) graid3
On Wed, Nov 24, 2004 at 09:20:33AM +0100, Michael Reifenberger wrote:
+ Hi,
+ since GEOM so a nicely layered framework (and I didnt want to loose my MBR)
+ I tried to setup a graid3 using using da1s1a... instead of da1...
+ getting the following negative results:
+ (not only trying to use
Hi,
to the best of my ability I have been investigating the 'real'
requirements of a raid-3 array, and cannot see that the following text
from graid3(8) cannot possibly be correct - and if it is, then the
implementation must be wrong or incomplete (emphasis added):
label Create a RAID3
On Wed, 24 Nov 2004, Pawel Jakub Dawidek wrote:
...
The thing you have to avoid (probably it should be more clear in the
manual page) is to allow providers to share the same last sector.
The gradi3 class uses the last provider's sector to store metadata
and if you have 2 or more providers which
On Wed, Nov 24, 2004 at 10:57:08AM +0100, Michael Reifenberger wrote:
+ On Wed, 24 Nov 2004, Pawel Jakub Dawidek wrote:
+ ...
+ The thing you have to avoid (probably it should be more clear in the
+ manual page) is to allow providers to share the same last sector.
+ The gradi3 class uses the last
Greetings,
out of fun and to investigate claims about alleged bgfsck resource
hogging (which I could not reproduce) posted to
news:de.comp.os.unix.bsd, I pressed the reset button on a live FreeBSD
5-STABLE system.
Upon reboot, fsck -p complained about an unexpected softupdates
inconsistency on
Matthias Andree wrote:
Greetings,
out of fun and to investigate claims about alleged bgfsck resource
hogging (which I could not reproduce) posted to
news:de.comp.os.unix.bsd, I pressed the reset button on a live FreeBSD
5-STABLE system.
Upon reboot, fsck -p complained about an unexpected
Scott Long [EMAIL PROTECTED] writes:
No, this in theory should not happen. YOu could have caught it right at
the instance that it was sending a transaction out to disk, or you could
have caught an edge case that isn't understood yet. Unfortunately, ATA
drives also cannot be trusted to flush
On Wed, 24 Nov 2004, Pawel Jakub Dawidek wrote:
...
The thing you have to avoid (probably it should be more clear in the
manual page) is to allow providers to share the same last sector.
The gradi3 class uses the last provider's sector to store metadata
and if you have 2 or more providers which
On Wed, Nov 24, 2004 at 03:41:50PM +0100, Michael Reifenberger wrote:
+ BTW: Is there a way to change a providers sectorsize (da1s1a in my case)
+ or ist it allways inherited from da1?
It is possible via dedicated GEOM class. There is no such class atm, which
changes provider's sector size and
Hi,
I was trying to update my 5.2.1 box to 5.3-RELEASE-p1.
I did this
cvsuped RELENG_5_3
make my KERNEL config
make buildworld
make buildkernel
make installkernel
shutdown now (At this time the machine was locked)
I rebooted the machine and enter in single mode with kernel 5.2.1
mergemaster -p
On Wed, 24 Nov 2004, Pawel Jakub Dawidek wrote:
...
Thanks for your informations!
Bye/2
---
Michael Reifenberger, Business Development Manager SAP-Basis, Plaut Consulting
Comp: [EMAIL PROTECTED] | Priv: [EMAIL PROTECTED]
http://www.plaut.de | http://www.Reifenberger.com
Date: Wed, 24 Nov 2004 10:35:46 +0900
From: Rob [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
Harlan Stenn wrote:
This would be use -g with ntpd and forget about ntpdate.
H
--
But make sure your clocks are in sink at the start by using date.
or add -g with the ntpdate_flags, to
Hi.
On Mon, Nov 22, 2004 at 05:02:00PM +0100, Uwe Doering wrote:
With the attached test program you'll probably find out soon whether PR
and fix apply to RELENG_5 (and possibly above) as well. Please keep us
posted.
I was able to DoS the machine (non-root user!) on 5-STABLE as of today
On Wed, Nov 24, 2004 at 10:54:07AM +0100, Eirik ?verby wrote:
+ to the best of my ability I have been investigating the 'real'
+ requirements of a raid-3 array, and cannot see that the following text
+ from graid3(8) cannot possibly be correct - and if it is, then the
+ implementation must be
In the last episode (Nov 24), Scott Long said:
Matthias Andree wrote:
out of fun and to investigate claims about alleged bgfsck resource
hogging (which I could not reproduce) posted to
news:de.comp.os.unix.bsd, I pressed the reset button on a live
FreeBSD 5-STABLE system.
Upon reboot,
Dan Nelson wrote:
In the last episode (Nov 24), Scott Long said:
Matthias Andree wrote:
out of fun and to investigate claims about alleged bgfsck resource
hogging (which I could not reproduce) posted to
news:de.comp.os.unix.bsd, I pressed the reset button on a live
FreeBSD 5-STABLE system.
Upon
Hello,
I am not able to operate atheros wireless cards with 4 port pci-pci
bridge. They are detected but they do not associate and they do other
weird stuff sometimes, like frequency not set correctly etc.
I believe this is a problem with the pci-pci bridge but I couldnt figure
out what I can
On 24. Nov 2004, at 18:11, Pawel Jakub Dawidek wrote:
On Wed, Nov 24, 2004 at 10:54:07AM +0100, Eirik ?verby wrote:
+ to the best of my ability I have been investigating the 'real'
+ requirements of a raid-3 array, and cannot see that the following
text
+ from graid3(8) cannot possibly be
Hi,
We are trying to create a jail with FreeBSD 5.3 but it's fails with this
error:
cc -O -pipe -I/usr/obj/usr/src/i386/legacy/usr/include -c
/usr/src/games/fortune/strfile/strfile.c
make: don't know how to make /j/usr/lib/libc.a. Stop
*** Error code 2
We was using:
export D=/j
make world
You were root, you'd done a mount -a, and the tree was local to the system?
I discovered the problem, my /tmp was mounted with noexec option, I
remove this and all worked fine.
Thanks a lot
--
Renato Botelho
ICQ: 54596223
AIM: RBGargaBR
___
[EMAIL
Hi,
I am upgrading by freebsd installation. While doing mergemaster, it
didn't ask me whether it should overwrite my /etc/motd file.
Is manual backing up of /etc/motd the only option or have I missed
something in mergemaster ?
Tejas Kokje
University of Southern California
Scott Long [EMAIL PROTECTED] writes:
I wonder if this points to dependencies not being pushed out of the
buffer/cache correctly.
So do I. Is there a good way to debug this, i. e. more systematic than
just trying to trash the FS and see if fsck can recover?
That said, I rarely, if ever, see
On Wed, Nov 24, 2004 at 11:30:24AM -0800, Tejas Kokje wrote:
I am upgrading by freebsd installation. While doing mergemaster, it
didn't ask me whether it should overwrite my /etc/motd file.
Is manual backing up of /etc/motd the only option or have I missed
something in mergemaster ?
By
On Wed, 24 Nov 2004 20:36:09 +0100, Matthias Andree [EMAIL PROTECTED] said:
I posted about softupdate problems on a SCSI system with DISABLED WRITE
CACHE, on a somewhat flakey Micropolis drive that froze and caused
If the hardware is broken, all bets are off, soft updates or no.
-GAWollman
On Wed, Nov 24, 2004 at 04:12:17PM -0300, Paulo Fragoso wrote:
Hi,
We are trying to create a jail with FreeBSD 5.3 but it's fails with this
error:
cc -O -pipe -I/usr/obj/usr/src/i386/legacy/usr/include -c
/usr/src/games/fortune/strfile/strfile.c
make: don't know how to make
On Wed, Nov 24, 2004 at 11:30:24AM -0800, Tejas Kokje wrote:
I am upgrading by freebsd installation. While doing mergemaster, it
didn't ask me whether it should overwrite my /etc/motd file.
Is manual backing up of /etc/motd the only option or have I missed
something in mergemaster ?
You
Matthias Andree wrote:
I posted about softupdate problems on a SCSI system with DISABLED WRITE
CACHE, on a somewhat flakey Micropolis drive that froze and caused
massive ffs+softupdates corruption in February 2004 (on FreeBSD 4
though), see URL:http://docs.freebsd.org/cgi/mid.cgi?m38yj15m59.fsf
Michael Nottebrock wrote:
Matthias Andree wrote:
I posted about softupdate problems on a SCSI system with DISABLED WRITE
CACHE, on a somewhat flakey Micropolis drive that froze and caused
massive ffs+softupdates corruption in February 2004 (on FreeBSD 4
though), see
Scott Long wrote:
Michael Nottebrock wrote:
Matthias Andree wrote:
I posted about softupdate problems on a SCSI system with DISABLED WRITE
CACHE, on a somewhat flakey Micropolis drive that froze and caused
massive ffs+softupdates corruption in February 2004 (on FreeBSD 4
though), see
Just hit a odd problem... here is what I am doing... I have a dvd+rw
drive that I am trying to export using ggated... of which some thing
is going wrong... any one have any idea what is happening?
I think I provided all the possible info, if any one can think of any
thing more, please let me
I did this
cvsuped RELENG_5_3
make my KERNEL config
make buildworld
make buildkernel
make installkernel
shutdown now (At this time the machine was locked)
I rebooted the machine and enter in single mode with kernel 5.2.1
mergemaster -p
make installworld
Well, this is not quiet right. You should
Can someone point me to what safe mode sets so I can debug whats
broke?
thanks
jim
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
On Thu, Nov 25, 2004 at 04:02:28PM +0900, Rob wrote..
Hi,
I thought 386 support had been removed since 5.X. But
http://www.freebsd.org/releases/5.3R/installation-i386.html
says:
1.2 Hardware Requirements
FreeBSD for the i386 requires a 486 or better processor to install
and run
Rob wrote:
Brian Szymanski wrote:
Did you try any machines that used Hyperthreading? I'd be interested to
see how those machines fare based on the number of logical and real CPUs.
Although people suggest -j4 as optimal in general
case, I have come to a very different conclusion:
1) single CPU
Wilko Bulte wrote:
On Thu, Nov 25, 2004 at 04:02:28PM +0900, Rob wrote..
Hi,
I thought 386 support had been removed since 5.X. But
http://www.freebsd.org/releases/5.3R/installation-i386.html
says:
1.2 Hardware Requirements
FreeBSD for the i386 requires a 486 or better processor to install
and
secmgr wrote:
Can someone point me to what safe mode sets so I can debug whats
broke?
thanks
jim
It disables ACPI, APIC, ATA DMA, ATAPI DMA, ATA Write Cache, and EISA.
Scott
___
[EMAIL PROTECTED] mailing list
Rob wrote:
Hi,
I thought 386 support had been removed since 5.X. But
http://www.freebsd.org/releases/5.3R/installation-i386.html
says:
1.2 Hardware Requirements
FreeBSD for the i386 requires a 486 or better processor to install
and run (although FreeBSD can run on 386 processors with a
Rob wrote:
Wilko Bulte wrote:
On Thu, Nov 25, 2004 at 04:02:28PM +0900, Rob wrote..
Hi,
I thought 386 support had been removed since 5.X. But
http://www.freebsd.org/releases/5.3R/installation-i386.html
says:
1.2 Hardware Requirements
FreeBSD for the i386 requires a 486 or better processor to
39 matches
Mail list logo
