-Original Message-
From: Ollivier Robert [SMTP:robe...@keltia.freenix.fr]
Sent: Thursday, March 18, 1999 12:26 AM
To: curr...@freebsd.org
Subject: Re: repeated ufs_dirbad() panics on 4.0-c
According to Mikhail A. Sokolov:
nope
/dev/da1e17235735 7414244
It seems Robert Nordier wrote:
If the problem is the bootblocks, why not send a message to Robert
Nordier, or if it's loader, to Mike Smith or Daniel Sobral? And
say, This is what I want to do, what are we going to do about it?
or something similar?
OK, easy enough, this is what I
This will require relabelling all of one class or the other (new
disklabel), or a major overhaul of the way that the root disk is found
inside the kernel. IMHO, the latter is where the change needs to
happen. SLICE might have made it a little easier, but searching won't
actually be all
SLICES, if done right, would make SO many things so much easier.
Poul-Henning
In message 199903180843.aaa01...@dingo.cdrom.com, Mike Smith writes:
This will require relabelling all of one class or the other (new
disklabel), or a major overhaul of the way that the root disk is found
inside
On Thu, Mar 18, 1999 at 12:25:57AM +0100, Ollivier Robert wrote:
# According to Mikhail A. Sokolov:
# nope
#
# /dev/da1e17235735 7414244 844263347%/mnt/arc
# /dev/da2e 8617355 1724705 689265020%/mnt/spool1
# /dev/da3e 8617355 1723638
Hello,
new 6 panics of such during the night. I'm gonna reproduce the machine
configuration without it using the IFT or any other but this precise IFT in
general today. The below mentioned are identical.
(Did I mention the rc knows about forced fsck -y only, no fsck -p or something?)
gdb -k
Is there a way in -current to manipulate the MTRR registers of recent
intel processors? I really want to make my framebuffer write-combined.
--
Frode Vatvedt Fjeld
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Dear FreeBSD'ers,
Can anybody explain why sysinstall (in post-install configuration mode)
trying mount already configured swap devices (disk label editor)? Is it
a bug or feature?
Maybe it will be useful to add routine which will check if swap is
already in use?
Sincerely,
Maxim Sobolev
To
On Thu, Mar 18, 1999 at 12:28:35PM +0300, Mikhail A. Sokolov wrote:
# Hello,
# panic: ffs_valloc: dup alloc
And a brand new one (for today):
IdlePTD 2682880
initial pcb at 21c7b8
panicstr: ffs_blkfree: freeing free frag
panic messages:
---
panic: ffs_blkfree: freeing free frag
#0 boot
Dmitry Valdov wrote:
I think that there is only one way to fix it - it's to disable making
*hard*links to directory with mode 1777.
I don't use quotas, and don't know a great deal about how they operate, but I
think there's another disk filling DOS involving hard links lurking which the
Andrew McNaughton wrote:
I don't use quotas, and don't know a great deal about how they operate, but I
think there's another disk filling DOS involving hard links lurking which the
above measure would also solve.
If a user starts making hard links to (large and growing) log files, with
On Fri, 19 Mar 1999, Andrew McNaughton wrote:
Dmitry Valdov wrote:
I think that there is only one way to fix it - it's to disable making
*hard*links to directory with mode 1777.
I don't use quotas, and don't know a great deal about how they operate,
but I think there's another disk
Matthew Dillon wrote:
:On Tue, Mar 16, 1999 at 12:52:32PM -0800, Matthew Dillon wrote:
: A.. And if you make those AMD mounts normal nfs mounts it doesn't
: fry? If so, then we have a bug in AMD somewhere.
:
:I tried the cp several times again on a regular NFS mount, to
On Thu, 18 Mar 1999 22:49:10 +0800, Peter Wemm pe...@netplex.com.au said:
AMD is easy to upset, and that's bad because it's holding a mountpoint in /
(ie: /host) which often gets hit by every single getcwd() call when it
gets a lstat(/host...) or whatever. I think this is the single largest
Hi folks,
19990316:
The name of the old wd.c and atapi.c based CDROM driver has
been changed back to wcd. So update your config file to use
device wcd instead of device acd.
Am I right in thinking that this only applies to people who are _not_
using Soren's new
Date: Wed, 17 Mar 1999 20:00:17 -0500 (EST)
From: David H. Brierley d...@galaxia.com
On any machine which allows general users to log in, I strongly
recommend making separate file systems for /, /usr, /tmp, and /home,
I'll merely point out (since the relevance to -current, per se, is
It seems Sheldon Hearn wrote:
Hi folks,
19990316:
The name of the old wd.c and atapi.c based CDROM driver has
been changed back to wcd. So update your config file to use
device wcd instead of device acd.
Am I right in thinking that this only applies to people
On Thu, 18 Mar 1999 16:57:32 +0100, Søren Schmidt wrote:
3 ?? I can only count two, the current one (now wcd) and my new one...
You're not as confused as I am. Thanks for the clarification. :-)
Ciao,
Sheldon.
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe
On Fri, 19 Mar 1999, Andrew McNaughton wrote:
Dmitry Valdov wrote:
I think that there is only one way to fix it - it's to disable making
*hard*links to directory with mode 1777.
I don't use quotas, and don't know a great deal about how they
operate, but I think there's another disk
On Thu, 18 Mar 1999, Robert Watson wrote:
The linking behavior in conjunction with quotas makes a lot of sense: if a
user wants to consume someone else's quota, she just hard links to their
files so they cannot delete them. And if she are mean, she links to them
in private directories so the
Hello!
What do think about add new version of BIND to -current?
Rgdz,
Sergey Osokin,
o...@etrust.ru
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
:On Thu, Mar 18, 1999 at 12:28:35PM +0300, Mikhail A. Sokolov wrote:
:# Hello,
:# panic: ffs_valloc: dup alloc
:
:And a brand new one (for today):
:
:IdlePTD 2682880
:initial pcb at 21c7b8
:panicstr: ffs_blkfree: freeing free frag
:panic messages:
:---
:panic: ffs_blkfree: freeing free frag
What do think about add new version of BIND to -current?
There have been some error reports against 8.2-REL, and I think we
should let it have a few more weeks to stabilize before it is brought
into -current.
(We're running 8.2 at some important name servers here, for instance
one which is
# Are you *sure* you're running -current as of today? Justin put code in to
# silence Illegal request error messages from the sync cache command.
These messages, since they are occurring only during a panic, are caused
by the code in dashutdown(). I didn't modify this code in my last checkin,
24 matches
Mail list logo
