y a pity. I'm using FreeBSD since version 2.05 and was never
disappointed.
Best regards
Matthias
--
Ciao/BSD - Matthias
Matthias Schuendehuette, Berlin (Germany)
- Matthew
--
Ciao/BSD - Matthias
Matthias Schuendehuette, Berlin (Germany)
it showed endless
requests from the client to release a lock and equally endless
error-replies...
At least I would expect that an error like that in kern/130628 would
look like what I observed today - but I may fail.
Thanks for your reply - Matthew
--
Ciao/BSD - Matthias
Matthias Schuendehuette, Berlin (Germany)
s mentioned, a new, non-productive server is available in the moment,
so tests are easily possible.
TIA
Matthew
--
Ciao/BSD - Matthias
Matthias Schuendehuette, Berlin (Germany)
est of *vinum* (without the "g") years ago when
I pulled the plug on one of the disks of a RAID5-plex...
Obviously there's no change at all concerning this problem.
- --
Ciao/BSD - Matthias
Matthias Schuendehuette, Berlin (Germany)
PGP-Key at and ID: 0xDDFB0A5F
-B
error!
I think it's *very* unlikely, that two machines have exactly the same
HW problems...
Matthew
- --
Ciao/BSD - Matthias
Matthias Schuendehuette, Berlin (Germany)
PGP-Key at and ID: 0xDDFB0A5F
-BEGIN PGP SIGNATURE-
Version: GnuPG
o compile krb5 on my laptop - a different machine,
which should not have the same memory problems...
- --
Ciao/BSD - Matthias
Matthias Schuendehuette, Berlin (Germany)
PGP-Key at and ID: 0xDDFB0A5F
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFE7LJif1BNcN37Cl8RAim
- --
Ciao/BSD - Matthias
Matthias Schuendehuette, Berlin (Germany)
PGP-Key at and ID: 0xDDFB0A5F
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFE7KW3f1BNcN37Cl8RAl3fAJsEtqiV7ttVyUruuEkWsZ130kyV0QCdHF7N
BkxAziq+7G6A/WtnSZkQNjo=
=FElW
-EN
7;m ready to test/try out.
--
Ciao/BSD - Matthias
Matthias Schuendehuette , Berlin (Germany)
PGP-Key at and ID: 0xDDFB0A5F
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
aviour to use proven technology[TM]
and let the cheap toys for the Linux-kiddies. It remains true: You
get what you pay for!
- --
Ciao/BSD - Matthias
Matthias Schuendehuette, Berlin (Germany)
PGP-Key at and ID: 0xDDFB0A5F
-BEGIN PGP SIGNATURE-
Version
ITSU-SIEMENS RX300 S2)...
what was my fault here? Should I post to -current instead?
- --
Ciao/BSD - Matthias
Matthias Schuendehuette, Berlin (Germany)
PGP-Key at and ID: 0xDDFB0A5F
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFC3+wAf1BNcN37Cl8RAkgOA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 15.07.2005 um 15:45 schrieb Matthias Schuendehuette:
I tried 6.0-BETA on one of our FUJITSU-SIEMENS RX300 S2 servers and
it seems that I have problems with the disk subsystem, even after
Scotts major overhaul of the mpt drivers...
I'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 15.07.2005 um 15:45 schrieb Matthias Schuendehuette:
I tried 6.0-BETA on one of our FUJITSU-SIEMENS RX300 S2 servers and
it seems that I have problems with the disk subsystem, even after
Scotts major overhaul of the mpt drivers...
I'
me to test, this machine
should become a Windoze printserver in about two or three weeks...
It seems to me that the HP DL380 is still the better machine... :-/
- --
Ciao/BSD - Matthias
Matthias Schuendehuette, Berlin (Germany)
PG
Hi Sean,
Am Sonntag, 13. März 2005 05:33 schrieb Sean Winn:
> On 13/03/2005, at 10:00 AM, Matthias Schuendehuette wrote:
> > Hi,
> >
> > since the last system update today (5.4-PRERELEASE) the
> > automountdaemon
> > amd(8) grabs port tcp/631 which prevents cu
Hi,
since the last system update today (5.4-PRERELEASE) the automountdaemon
amd(8) grabs port tcp/631 which prevents cupsd(8) from starting which
in turn prevents smbd(8)/SAMBA from starting.
How come? Have I overlooked something?
--
Ciao/BSD - Matthias
Matthias Schuendehuette , Berlin
Hi Scott,
Thanks for you reply.
Am Freitag, 4. März 2005 06:10 schrieb Scott Long:
> Matthias Schuendehuette wrote:
> >
> > The error message is: "xsysinfo: undefined symbol: _nfiles"
> >
> > I had the belief, that this does not happen within a major release
Hi,
yesterday (MAR02,2005) I updated to 5.4-PRERELEASE. Since then,
'xsysinfo-1.4a' doesn't run anymore.
The error message is: "xsysinfo: undefined symbol: _nfiles"
I had the belief, that this does not happen within a major release of
FreeBSD... isn't it?
--
now mounted with
> /usr) is already known. Well, dont know what gvinum is tying to tell
> me here.
What?! Did you mount it? Or is it still mentioned in /etc/fstab but not
mounted any more...
If you *did* mount /dev/ad0s1e as /usr you should start from the
beginning reading the vinum(8) man
tem has come up and the main partitions are mounted.
If all these points don't leed to an solution, perhaps contact Lukas
Ertl ([EMAIL PROTECTED]) directly, which is the maintainer of gvinum...
--
Ciao/BSD - Matthias
Matthias Schuendehuette , Berlin (Germany)
PGP-Key at and ID: 0xDDFB0
Hello,
Am Samstag, 5. Februar 2005 21:06 schrieb Dominique Goncalves:
> I have had the same problem exactly today.
> Re cvsup your src tree and rebuild kernel and world solved this
> problem.
Yes, indeed. Thanks a lot!
--
Ciao/BSD - Matthias
Matthias Schuendehuette , Berlin (Germany
ns the number of processes in the system
run queue averaged over various periods of time."
So - what's going on here?
--
Ciao/BSD - Matthias
Matthias Schuendehuette , Berlin (Germany)
PGP-Key at and ID: 0xDDFB0A5F
___
freebsd-stable@freebs
fix the disks for geom_vinum compability, or do they need
> to be rebuilt from the ground up?
I don't know any hints any more, sorry. I send a pointer to
[EMAIL PROTECTED], which is the creator of geom_vinum, because he follows
-current and not -stable AFAIK.
--
Ciao/BSD - Matthias
ar now...
> Perhaps I am ignorant, but it seems to me it would have been easier
> to make the regular vinum diver handle geom drives in place of making
> a new kernel object? Or perhaps theres a technical reason for not
> doing so?
Exactly that's the case. If you have to use a c
#x27;s little more you can do to
> get the "failed" drive recognised as being in the "up" state other
> than to reboot. [...]
'gvinum setstate' was MFCed from -current together with 'gvinum
checkpatity' and 'gvinum rebuildparity' a week ago
n offest of "0" (zero) within the slice
(da0/da1) or disk (ad0) respectively.
*If* that's the case (i.e. Offset of 0 for the vinum partitions), you
have a problem indeed but otherwise I would not expect any problems.
--
Ciao/BSD - Matthias
Matthias Schuendehuette , Berlin (Germany
Hi,
Am Montag, 15. November 2004 19:41 schrieb Paul Mather:
> On Mon, 2004-11-15 at 19:33 +0100, Matthias Schuendehuette wrote:
> > The extension of filesystems on concat plexes works (simply) as
> > advertised... :-) At least *I* had no problems so far.
>
> That's enc
s. I use (g)vinum primarily as a LVM with concat plexes on
ProLiant Servers with SmartRAID-Controllers, so mirroring and/or RAID5
is done in hardware.
The extension of filesystems on concat plexes works (simply) as
advertised... :-) At least *I* had no problems so far.
--
Ciao/BSD - M
27;t mean that I'm not trying to help to get gvinum to
the place and state where it deserves to be... :-)
--
Ciao/BSD - Matthias
Matthias Schuendehuette , Berlin (Germany)
PGP-Key at and ID: 0xDDFB0A5F
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Am Sonntag, 7. November 2004 06:30 schrieb secmgr:
> On Sat, 2004-11-06 at 04:16, Matthias Schuendehuette wrote:
> > Did you try to simply 'start' the plex? This works for
> > initialisation of a newly created RAID5-Plex as well as for
> > recalculating parity inform
angling vnode'-problem with "vinum-classic":
Try to start 'classic' vinum *after* the system has come up. Either
manually or perhaps with a script in /usr/local/etc/rc.d. This works
for me until now under 5-STABLE (a.k.a. RELENG_5).
--
Ciao/BSD - Matthias
Matthias Schuen
initialisation of
a newly created RAID5-Plex as well as for recalculating parity
informations on a degraded RAID5-Plex.
It's that simple (at least for me on 5-STABLE) but admittedly
undocumented.
--
Ciao/BSD - Matthias
Matthias Schuendehuette , Berlin (Germany)
PGP-Key at and ID: 0
1 for -STABLE, disk #2+#4
are for -current. I want to boot -stable, so I try to load the RAM-Disk
Image from disk #1 - but it's crashed. How do I know what disk to use
next?
Please answer per Mail too, I'm reading this list via docs.freebsd.org
--
Ciao/BSD - Matthias
Matthias Schu
all crap. It's obviously the best driver we *have*
and obviously the most knowledgeable ATA-Programmer who's working for
'our' FreeBSD and we should appreciate that.
--
Ciao/BSD - Matthias
Matthias Schuendehuette <[EMAIL PROTECTED]>, Berlin (Germany)
Powered by FreeBSD
c_flags & ~CALLOUT_PENDING);
129 }
130 splx(s);
131 c_func(c_arg);
132 s = splhigh();
133 steps = 0;
134 c = ne
these problems, in the german bsd-newsgroup are at
least two other persons with exactly the same problems...
Please have a look on that issue. If I can do any further testing, I'll
do it ASAP.
Ciao/BSD - Matthias
--
***
Hi,
On 19-Aug-01 Matthias Schuendehuette wrote:
>
> there's a showstopper in 4.4-RC1 as of Sat, 18th Aug, around 18:00 UTC:
>
> My machine stopps booting after submitting the SCSI-Reset command to
> both
> of my 'sym'-Controllers.
>
Just for information: T
-PRE Issue,
but at least, it happens now.
Can anybody confirm this?
BTW: I have my /usr/obj on a vinum RAID5-volume and it works perfectly
stable! Only this shutdown-restart sequence is in the moment an absolute
No-No
Ciao/BSD - Matthias
--
Matthias Schu
38 matches
Mail list logo