Hi!
I'm having troubles updating a FreeBSD 3-stable system to current, since it has /usr
as a vinum volume. I've just updated about a dozen machines without any problems, but
none of them uses vinum.
Following the instructions in UPDATING, when rebooting to single user mode, vinum
wouldn't
Alfred Perlstein wrote:
Yowch, please wrap lines at 70 characters. :)
Oops! Sorry about that. I had fiddled with the settings for a
specific purpose, and forgot to set them back. :-/
Read the loader page carefully and you should be able to boot 3.x
kernels with 3.x modules and 4.0 modules
Warner Losh wrote:
In message [EMAIL PROTECTED] "Daniel C. Sobral" writes:
: make buildworld
: make buildkernel
: make installkernel
: MAKEDEV
: reboot single user
: make -DNOINFO installworld
: make installworld
:
: As you see, the new klds don't get installed in the presently
Greg Lehey wrote:
[Format recovered--see http://www.lemis.com/email/email-format.html]
On Saturday, 18 March 2000 at 3:34:38 +0100, Palle Girgensohn wrote:
Hi!
Please don't send messages one line per paragraph. It's a pain to
reformat.
Yeah, I had had fiddled with the setting
Hi!
I'm having a strange problem after upgrading: There are no raw
devices created for vinum volumes. This makes dump(8) puke.
This is a 3.4 system:
ls -laF /dev/vinum
...
crwxr-xr-- 1 root wheel 91, 1 2 Jul 1999 rusr*
drwxr-xr-x 2 root wheel 512 2 Jul 1999 rvol/
...
Hello again.
I did some rtfm and src digging, it appears the listing I gave is
correct; the raw devices are in the rvinum dircetory. Problem is,
dump looks in vinum/r*. There seems that vinum introduces a bug
here, since dump's rawname function replaces the last '/' in the
device name with '/r'.
This fixes it for me. Is my installation faulty, or is this
something that vinum fails to do when creating its devices?
#! /bin/sh
cd /dev/vinum
for i in ../rvinum/*; do ln -s $i r`basename $i`; done
/Palle
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in
Greg Lehey wrote:
On Tuesday, 21 March 2000 at 14:48:55 +0100, Palle Girgensohn wrote:
Hi!
I'm having a strange problem after upgrading: There are no raw
devices created for vinum volumes.
Indeed there are. You list them below. There are no longer any block
devices
, no mirror or raid at all, on top of a
ciss raid-5, and it failed with RC1. [trying RC2 now, but seems nothing is
changed?].
Anyone up to the task of finding this culprit, we can let you into the machine
remotely through the iLO. Please let me know.
Best reagards
Palle Girgensohn
girgen
23 nov 2011 kl. 02:20 skrev Sean Bruno sean...@yahoo-inc.com:
On Tue, 2011-11-22 at 14:59 -0800, Palle Girgensohn wrote:
Hi,
When installing 9.0 RC1 on our HP servers, we of course wanted to use gpt
intead of fdisk. However, it doesn't work.
First I tried gptzfsboot, it failed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks,
We can chack it out, we are about to reinstall a machine. Migth be a HP
DL380 *G6* though, does that matter?
Andriy Gapon skrev:
Guys,
if you still have the hardware and use FreeBSD, could you please try
r243025?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yes, this work like a charm. Super! Booted with no problems. Well done!
Palle
Andriy Gapon skrev:
Guys,
if you still have the hardware and use FreeBSD, could you please try
r243025?
http://svnweb.freebsd.org/base?view=revisionrevision=243025
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This was for an HP DL380 G5, by the way.
I'll try it on a G6 later as well, I reckon the outcome will be similar.
Palle
Andriy Gapon skrev:
Guys,
if you still have the hardware and use FreeBSD, could you please try
r243025?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry, jumped the gun here... it booted first time, now it is back at
the same fail prompt...
gptzfsboot: error 1 lba 32
gptzfsboot: error 1 lba 1
gptzfsboot: No ZFS pools located, can't boot
Andriy Gapon skrev:
Guys,
if you still have the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Palle Girgensohn skrev:
Hi!
This is still happening with FreeBSD 9.0-RELEASE, as I have just
discovered. The hack works like a charm, but seems kind of odd... :)
Any progress in getting a real fix into the repository? Any risks
with the hack
10 jan 2013 kl. 18:15 skrev John Baldwin j...@freebsd.org:
On Wednesday, January 09, 2013 05:57:06 PM Palle Girgensohn wrote:
Palle Girgensohn skrev:
Hi!
This is still happening with FreeBSD 9.0-RELEASE, as I have just
discovered. The hack works like a charm, but seems kind of odd
Hi!
This is still happening with FreeBSD 9.0-RELEASE, as I have just
discovered. The hack works like a charm, but seems kind of odd... :)
Any progress in getting a real fix into the repository? Any risks with
the hack - is it likely to believe that it will suddenly or sporadically
fail?
Cheers,
is variable-length). This fixes data smashing problems
from passing an EDD 3 structure to BIOSes supporting EDD 4.
Approved by:re (kib)
--
Christoph Hoffmann
On Mar 1, 2012, at 10:39 PM, Palle Girgensohn wrote:
Hi!
This is still happening with FreeBSD 9.0-RELEASE, as I have
5 mar 2012 kl. 22:16 skrev John Baldwin j...@freebsd.org:
On Monday, March 05, 2012 2:35:59 pm Palle Girgensohn wrote:
5 mar 2012 kl. 18:39 skrev John Baldwin j...@freebsd.org:
On Saturday, March 03, 2012 7:06:14 pm Christoph Hoffmann wrote:
Hello,
I think this bug has been fix
27 jun 2014 kl. 18:34 skrev Konstantin Belousov kostik...@gmail.com:
On Fri, Jun 27, 2014 at 10:57:53AM -0400, John Baldwin wrote:
On Friday, June 27, 2014 8:56:13 am Konstantin Belousov wrote:
Hi,
I did some measurements and hacks to see about the performance and
scalability of PostgreSQL
28 jun 2014 kl. 12:21 skrev Konstantin Belousov kostik...@gmail.com:
On Sat, Jun 28, 2014 at 12:08:39PM +0200, Palle Girgensohn wrote:
27 jun 2014 kl. 18:34 skrev Konstantin Belousov kostik...@gmail.com:
On Fri, Jun 27, 2014 at 10:57:53AM -0400, John Baldwin wrote:
On Friday, June
Hi!
I'm experiencing some strange errors with one of our workstations. I
recently moved all of our workstations to 3.0 current as of 1998-12-18.
Does any of this make any sense to anyone:
trumpet:~rlogin balalaika
netd in free(): warning: junk pointer, too low to make sense.
trumpet:~telnet
(Sorry for the crosspost, but I'd like to now if this is fixed in -current)
Hi!
I've seen three crashes in the last couple of weeks, with a server box that's
been running stable as a rock for two years, at least. It has an adaptec 2940UW
with six disks, and an adaptec 1542CP that's connected to
this is not the easiest thing to debug; I had to sit and watch
the screen for 90 minutes before it happened...
Drop me a mail if you find anything. Thanks!
/Palle
Warner Losh wrote:
In message 36d4b092.8b076...@partitur.se Palle Girgensohn writes:
: I've seen three crashes in the last couple
24 matches
Mail list logo
