On Sun, 2006-11-26 at 19:23, Richard Coleman wrote:
I just bought a large external hard drive for home backups (500g Western
Digital My Book). When I
plug it in to my machine (RELENG_6 from about a week ago), the system sees
the device just fine:
Nov 26 22:03:21 neptune kernel: umass0:
On Sun, 2006-11-26 at 22:09, Clayton Milos wrote:
As far as I am aware windows 2000 and xp will only allow you to format up to
a 32G dive with FAT32. Any bigger and it will force you to use NTFS. The
other strange thing is tht you are trying to mount /dev/da0 and not
/dev/de0s1.
The 32
Chris Dillon wrote:
I had problems with snapshots and hangs in 5.x. For that, a daily
reboot would keep the problems at bay. I upgraded to 6.0 and the
problems completely disappeared. I kept 6.0-STABLE running for weeks.
Somewhere along the line, as 6.1 approached, similar problems
Anton Nikiforov wrote:
Today we were changing power supply so we shut all servers down at 17:00.
After changing of UPS we start everything up and my LSI controller
starts to claim that disk and NVRAM configuration mismatch.
Okay, not really a FreeBSD issue. Which adapter are you using? They
Peter Jeremy wrote:
On Wed, 2005-Dec-07 13:34:53 -0800, Vizion wrote:
That is a judgment call - franky my experience has been that developers who
are bad at ensuring their work is well documentated are second rate rather
than top rate developers.
Software developers are notoriously
Christian Brueffer wrote:
On Thu, Dec 08, 2005 at 12:18:57AM +0100, Torfinn Ingolfsen wrote:
In short, don't write gvinum off just yet. Documentation is around the
corner (as a result of a SoC project).
Actually gvinum(8) has been committed to CURRENT and RELENG_6 a couple
of days
Doug Barton wrote:
How does this change to UPDATING in RELENG_6 look to you:
Index: UPDATING
===
RCS file: /home/ncvs/src/UPDATING,v
retrieving revision 1.416.2.7
diff -u -r1.416.2.7 UPDATING
--- UPDATING1 Nov 2005 23:44:40
Kris Kennaway wrote:
On Tue, Dec 06, 2005 at 01:20:44PM -0800, Vizion wrote:
On Tuesday 06 December 2005 11:47, the author Vizion contributed to the
dialogue which was on-
Re: Upgrading 5.3 6.0 buildworld failure in libkrb5 but is currently:
Upgrading 5.3 6.0 buildworld failure now in
Kris Kennaway wrote:
On Tue, Dec 06, 2005 at 02:36:05PM -0700, secmgr wrote:
Update to 5.4 before trying to update to 6.0.
Kris
So is there any supported direct 5.3-6.0 upgrade path, or is a stop in
5.4 ville manditory now.?
I tried to say that you have to update to 5.4
Peter Orlowski wrote:
On Tue, May 10, 2005 at 11:24:12AM -0600, secmgr wrote:
Gabor Esperon wrote:
How reliable is the gmirror subsystem?
gmirror seems fine as best as I can tell. I've been running it for a
few months on sata drives.
I had gmirror running on two IDE drives
Edwin Brown wrote:
All:
I've been asked to setup a RAID-5 server using software raid. I've not
worked with gvinum or vinum for that matter. I know from following the
mailing lists there have been some concerns over gvinum in the
5.3-RELEASE. How are things working today?
The plan would be use a
Gabor Esperon wrote:
How reliable is the gmirror subsystem?
gmirror seems fine as best as I can tell. I've been running it for a
few months on sata drives.
jim
___
freebsd-stable@freebsd.org mailing list
I'm building a usb harddrive and i'll be using it under both linux and
FreeBSD. vfat is not a contender due to a 2gb limit of file size (I'm
using it as a dump disk and I don't want to deal with multiple
volumes). It seems that BSD can talk to ext2 partitions and Linux can
talk to the older
secmgr wrote:
I just picked up a new ABIT NF7-S2G motherboard (NF2 MCP chip set with
gigE and SATA/RAID). I'm running 5.3 release on it. The standard
parallel ATA chipset returns a known id . The SATA i/f seems to be
too new, and freebsd treats it like an unknown udma33 controller
Rob MacGregor wrote:
On Friday, March 11, 2005 5:26 PM, secmgr unleashed the infinite monkeys and
produced:
Failing that, is there a definitive list of SATA PCI boards which
FreeBSD does full support?
See the release notes for the version of FreeBSD you're using. For 5.3 that's
http
I just picked up a new ABIT NF7-S2G motherboard (NF2 MCP chip set with
gigE and SATA/RAID). I'm running 5.3 release on it. The standard
parallel ATA chipset returns a known id . The SATA i/f seems to be
too new, and freebsd treats it like an unknown udma33 controller.
There's no Marvel
Michael Nottebrock wrote:
Hanspeter Roth wrote:
The problem here is, that the Beastie picture is disabled by
default. This is obviously not compatible with the majority of
people.
You're not up-to-date with the latest events, the beasty menu was
completely nuked from CVS yesterday after the most
On Thu, 2004-11-25 at 00:22, Scott Long wrote:
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
Many thanks! I tried disabling ATA/ATAPI DMA
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]
Tejas Kokje wrote:
Hi,
I am trying to do buildkernel with my own configuration file
(MYKERNEL_CONFIG). I am getting the following error. I am not sure
what is wrong. Any help will be appreciated .
# uname -sr
FreeBSD 4.9-RELEASE-p11
#make buildkernel KERNCONF=MYKERNEL_CONFIG
Sam wrote:
Also, i kicked up gvinum to compare, but he doesn't seem to
have a stripe command (despite saying he does in the help).
there is a geom stripe class called gstripe thats outside of the gvinum
user interface.
jim
___
[EMAIL PROTECTED] mailing
Matthias Schuendehuette wrote:
I'm not sure if this is a problem of (g)vinum or if FreeBSD has other
problems in this area.
just logged a kern bug on this
And we all have to consider that gvinum is in a relatively early
development phase (IMHO) - it is basically working, that is, it's
ok, your instructions worked like a charm. So i'm running my nice 4
member SCSI gvinum raid5 array (with softupdates turned on), and it's
zipping along. Now I need to test just how robust this is. camcontrol
is too nice. I want to test a more real world failure. I'm running
dbench and
It did, but can you tell me anywhere in the docs it says to do that? Or
maybe that vinum should sense that and throw some error rather than just
blindly corrupting itself.
jim
On Sun, 2004-11-07 at 09:38, Joe Koberg wrote:
secmgr wrote:
No, I mean self corrupting raid5 sets during
No, I mean self corrupting raid5 sets during initialization. Discussed
about 2-3 weeks ago.
On Sat, 2004-11-06 at 05:09, Matthias Schuendehuette wrote:
If you mean the 'dangling vnode'-problem with vinum-classic:
Try to start 'classic' vinum *after* the system has come up. Either
I did a gvinum start.
On Sat, 2004-11-06 at 04:16, Matthias Schuendehuette wrote:
Am Mittwoch, 3. November 2004 21:27 schrieb secmgr:
Just ran into this myself. I had a perfectly happy raid 5 plex under
5.3 RC1. I upgrade to RC2, and the whole plex goes stale. I deleted
everything from
Adrian Wontroba wrote:
On Mon, Nov 01, 2004 at 10:05:16AM +1100, Carl Makin wrote:
Do you want to yank it in 5 or 6-CURRENT? There are a *lot* of people
using vinum and yanking it in 5-STABLE would force us all to use the 5.3
security branch until gvinum caught up.
From my experiences
Greg 'groggy' Lehey wrote:
A bit of background: we know that 'gvinum' will replace Vinum; the
original intention had been to do it seamlessly, but for various
reasons that did happen. Then we decided that we should leave them
both in the tree until gvinum had the full functionality of Vinum.
It's
Marko Raiha wrote:
Hi,
On Wed, Oct 27, 2004 at 09:10:39AM -0600, secmgr wrote:
The reason is empirically derived. When I created a 7 disk raid 5 set
using len 0 or all the space available, the raid set would be corrupt
after initializing. Every time. When I reserved back that extra
space
Chuck Swiger wrote:
No. All of the drives need to be the same size. With RAID-5, which
drive is used to hold parity data rotates on a stripe-by-stripe basis
to balance out the load.
Just to clarify this point. All the subdisks in the plex need to be the
same size. The physical drives and
Marko Raiha wrote:
Hi,
On Tue, Oct 26, 2004 at 11:33:43PM -0600, secmgr wrote:
...
when you define the subdisk, don't use the whole drive. Leave at least
64 blocks unused.
...
Would you mind to tell the reason behind this rule of leaving at least
64 blocks unused?
Regards,
The reason
On Tue, 2004-10-26 at 18:27, Mikhail P. wrote:
I haven't worked with Vinum previously, but hear a lot about it. My question
is how to implement the above (unite four drives into single volume) using
Vinum, and what will happen if let's say one drive fails in volume? Am I
loosing the whole
I have freebsd 5.3 rc1 installed perfectly, i configure vinum with the handbook and
all work perfect
but when try run vinum with rc.conf there display the error:
panic: unmount: dangling vnode
cpuid: 0
uptime= 4s
Cannot dump. No dump device defined
Automatic reboot in 15 seconds.
why happened ?
Andrew Konstantinov wrote:
On Mon, 2004-10-25 at 05:55, Oliver Torres Delgado wrote:
I have freebsd 5.3 rc1 installed perfectly, i configure vinum with the handbook and
all work perfect
but when try run vinum with rc.conf there display the error:
panic: unmount: dangling vnode
cpuid: 0
uptime=
I've got 7x9.1 gig scsi drives off an adaptec AIC7880 class controller.
(da0-6). I want to raid5 these using vinum. I'm a newbie with vinum.
If I use a bsd partition the same size as the slice (c=h), and then let
the subdisks use the entire partition (len 0), the raid set is corrupted
every
35 matches
Mail list logo
