In message 01e701c2b62b$db07ddd0$471b3dd4@dual, Willem Jan Withagen writes:
I was able to copy the full 100+Gb.
Next I'm going to try and fill the disk to the max as user, but i guess it'll not
trigger this bug.
And to that fact I have a question:
At the moment 8% of the disk is reserved.
In message [EMAIL PROTECTED], Nate Lawson wri
tes:
I'd like to have a mirrored root partition. I tried ccd(4) but the boot
blocks couldn't find the fs. Any idea how much work it would take to
enable booting a ccd root? Also, does vinum already support this?
The best way to do this is to get a
In message [EMAIL PROTECTED], walt writes:
After updating world and kernel this evening I saw this message fly by
during the reboot:
Mounting root from ufs:/dev/ad0s3a
VOP_STRATEGY on VCHR
: 0xc25fd000: tag none, type VCHR, usecount 5, writecount 0, refcount 6, flags
(VV_OBJBUF),
Sorry, need
In message 063601c2b4d0$ff02dc50$471b3dd4@dual, Willem Jan Withagen writes:
Recompiled the kernel (GENERIC) and installed.
But now it panics on:
Initiate_write_inodeblock_ufs1: already started.
When does it panic ? in the boot sequence ? after ?
Can you get me the first 4-5 lines of the
In message [EMAIL PROTECTED], Bruce Evans writes:
The following change uncovers bugs in specfs locking and other places:
Wow, that was fun! :-/
I always wondered why specfs would insist on no locking, but I never
had much ambition for finding out.
Fixing specfs is simple:
This is not tested
In message [EMAIL PROTECTED], Bruce Evans writes:
On Sun, 5 Jan 2003 [EMAIL PROTECTED] wrote:
I always wondered why specfs would insist on no locking, but I never
had much ambition for finding out.
Me too. It seems to be mostly a mistake.
Fixing specfs is simple:
This is not tested with
In message [EMAIL PROTECTED], Robe
rt Watson writes:
While debugging the recent pthreads problem, I've started running into
this:
pid 663 (test), uid 1000: exited on signal 10 (core dumped)
failed to set signal flags properly for ast()
failed to set signal flags properly for ast()
failed to set
In message [EMAIL PROTECTED], Paul A. Mayer writes:
Hi,
I had to install the e2fstools port before I could access my e2fs
partitions after installing -current. Thereafter everything has been
fine. No problems with the disk, etc. The only thing that is a problem
is if your e2fs partion(s)
In message [EMAIL PROTECTED], David O'Brien writes:
On Sun, Jan 05, 2003 at 05:01:15PM +0100, [EMAIL PROTECTED] wrote:
In message 063601c2b4d0$ff02dc50$471b3dd4@dual, Willem Jan Withagen writes:
But now it panics on:
Initiate_write_inodeblock_ufs1: already started.
When does it panic ?
In message [EMAIL PROTECTED], Bruce Evans writes:
No. Also no INVARIANTS and the like. A profiling kernel (with profiling
not running) seemed to panic faster.
Ok, in this case listening to KASSERTS would probably have helped you.
Please try 1.351 of vfs_bio.c
--
Poul-Henning Kamp |
In message [EMAIL PROTECTED], Rahul Siddharthan
writes:
# e2fsck -n /dev/ad0s2
e2fsck 1.27 (8-Mar-2002)
The filesystem size (according to the superblock) is 714892 blocks
The physical size of the device is 0 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort? no
In message [EMAIL PROTECTED], Rahul Siddharthan
writes:
[EMAIL PROTECTED] wrote:
# e2fsck -n /dev/ad0s2
e2fsck 1.27 (8-Mar-2002)
The filesystem size (according to the superblock) is 714892 blocks
The physical size of the device is 0 blocks
Either the superblock or the partition table is
That one should already be fixed.
In message [EMAIL PROTECTED], Peter Kostouros writes:
Hi
I received a similar problem during booting into single user mode upon
startup. I hope the following helps:
mounting root from ufs:/dev/ad2s1a
start_init: trying /sbin/init
VOP_STRATEGY on VCHR
In message 03a701c2b38c$8e3ad990$471b3dd4@dual, Willem Jan Withagen writes:
Which seems a problem sticking up it's head once so often.
I had it happen to me now 3 times over the last day. It just drops into the debugger.
And I've foun little extra info in the archive.
What dows this actually
In message [EMAIL PROTECTED], David Holm writes:
Hi,
I tried upgrading this morning but compilation fails with the following error
(I waited a while and cvsup'd again in case someone was commiting, didn't
help)
It seems like your #includes are not in sync with your userland,
did you use make
In message [EMAIL PROTECTED], Hiroki Sato writes:
I also had kmem_malloc(4096): kmem_map too small: 275378176 total allocated
several times on -current as of Jan 4th. My -current box has 3GB memory,
but when the memory size is explicitly specified as 2GB via MAXMEM option,
the panic
In message [EMAIL PROTECTED], Peter Wemm writes:
Peter Wemm wrote:
Kris Kennaway wrote:
--AhhlLboLdkugWU4S
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Can someone please fix whereintheworld to grok the new make regression
test output, so it doesn't get
In message 051f01c2b42e$e4651400$471b3dd4@dual, Willem Jan Withagen writes:
But the following question is alrady there.
When I woke up this morning I found my box with a double panic:
lock (sleep mutex) VM page queue mutex not locked @
/usr/src/sys/kern/vf
[the remainder was not on the
In message [EMAIL PROTECTED], Trent Nelson writes:
I've written an extension to systat that allows you to monitor the
traffic through active network interfaces on the system, akin to
netstat -I. I've attached the patch to this e-mail, but it can also be
found at
Committed, thanks!
Poul-Henning
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to
In message [EMAIL PROTECTED], Takahashi Yoshihiro
writes:
In article [EMAIL PROTECTED]
Poul-Henning Kamp [EMAIL PROTECTED] writes:
I think you need to either #ifdef something here (and there may be
more some similar code in places like truss or the debugger) or
alternatively rename the
In message [EMAIL PROTECTED], Bruce Evans writes:
% Index: vm_swap.c
% ===
% RCS file: /home/ncvs/src/sys/vm/vm_swap.c,v
% retrieving revision 1.127
% retrieving revision 1.128
% diff -u -1 -r1.127 -r1.128
% --- vm_swap.c3 Jan
In message [EMAIL PROTECTED], Ju
lian Elischer writes:
We have some software we'd like to behave slightly differently if it is
in a jail.
What methods do people use to detect they are in a jail?
procfs/curproc might work but I don't want to depend on procfs.
ps aux can be used but seems rather
In message [EMAIL PROTECTED], Ju
lian Elischer writes:
Use sysctl to pick up your own proc, look for the jail flag. It takes
less than 10 lines of C.
I can't see anything relevant in sysctl -a.
We don't return binary blobs from sysctl -a.
--
Poul-Henning Kamp | UNIX since Zilog Zeus
In message [EMAIL PROTECTED], Bruce Evans writes:
The md driver doesn't set any of the si_ size parameters so it has no chance
of getting this stuff right when the parameters are not the defaults.
It does however set its sectorsize to 4k. The problem was GEOM not
setting si_bsize_phys on the
In message [EMAIL PROTECTED], Bruce Evans writes:
On Thu, 2 Jan 2003 [EMAIL PROTECTED] wrote:
In message [EMAIL PROTECTED], Bruce Evans writes:
The md driver doesn't set any of the si_ size parameters so it has no chance
of getting this stuff right when the parameters are not the defaults.
In message [EMAIL PROTECTED], Andrey Koklin writes:
Hi folks,
Silly question, perhaps, but I wasn't able to figure out source of the
problem myself...
I used rarely magneto-optical disks to transfer data to/from Windows
machine. For compatibility, disks used HDD FAT16 format.
About a month ago
In message [EMAIL PROTECTED], Jos Backus writes:
Accompanied by
Dec 28 01:42:12 lizzy kernel: spec_getpages:(md0) I/O read failure: (error=22) bp
0xce5f9310 vp 0xc41e8708
Dec 28 01:42:12 lizzy kernel: size: 2048, resid: 2048, a_count: 2028, valid: 0x0
Dec 28 01:42:12 lizzy kernel:
In message [EMAIL PROTECTED], Jos Backus writes:
On Sat, Dec 28, 2002 at 08:39:32PM +0100, [EMAIL PROTECTED] wrote:
22 is EINVAL, so likely cause is a bogus offset. Either unaligned or
out of range. Unfortunately the above messages does not contain the
offset of the I/O operation.
Suggest
In message [EMAIL PROTECTED], Poul-Henning Kamp
writes:
phk 2002/12/27 03:05:05 PST
Modified files:
sys/ufs/ffs ffs_vfsops.c
Log:
Use three UMA zones for FFS/UFS inodes instead of malloc space.
Since inodes are currently 144 bytes, this will save 112 bytes per
In message [EMAIL PROTECTED], Craig Rodrigues writes:
On Wed, Dec 25, 2002 at 05:37:46AM -0800, Kris Kennaway wrote:
On Tue, Dec 24, 2002 at 01:31:10PM -0500, Craig Rodrigues wrote:
Any ideas what the problem could be?
geom seems to have anti-foot-shooting measures in place to disallow
In message [EMAIL PROTECTED], Craig Rodrigues writes:
On Wed, Dec 25, 2002 at 10:12:12PM +0100, [EMAIL PROTECTED] wrote:
The result of this is that I booted off of a slice contained on the
/dev/ad0 disk, then I cannot add new partitions to /dev/ad0
with sysinstall, even if I am root.
In message [EMAIL PROTECTED], Paul A. Scott writes:
--
From: Poul-Henning Kamp [EMAIL PROTECTED]
void setctty(char *name) {
(void) revoke(name);
if ((fd = open(name, O_RDWR)) == -1) {
Isn't there a pretty obvious race between the revoke() and the open() ?
Wouldn't it in fact
In message [EMAIL PROTECTED], Paul A. Scott writes:
I think you missed the fine point in the kick everybody *else*
off comment.
Ahhh. I guess you mean that revoke() would change to do that. You're right,
I did miss your point.
The point is you cannot serialize against other processes.
But
In message [EMAIL PROTECTED], Garrett Wollman
writes:
On Tue, 24 Dec 2002 12:40:25 +0100, Poul-Henning Kamp [EMAIL PROTECTED] said:
Isn't there a pretty obvious race between the revoke() and the open() ?
To the extent that the race matters, it is obviated by making sure
that only the current
This is 100% identical to my panic.
My system is a dual athlon/2G system too.
In message [EMAIL PROTECTED], David O'Brien writes:
---
#0 doadump () at ../../../kern/kern_shutdown.c:232
232dumping++;
(kgdb) bt
#0 doadump () at ../../../kern/kern_shutdown.c:232
#1 0xc01eac9e in
In message [EMAIL PROTECTED], Brian J. McGov
ern writes:
I was just going through the list of projects at the FreeBSD website. I
didn't see one for the installer. I was curious if anyone was working on
an upgrade/replacement for sysinstall... I know of Jordan's paper on the
subject, et al, but
In message [EMAIL PROTECTED], Thorsten Greiner w
rites:
Hi,
I just tried to compile 5.0-RC2 from using a recently cvsupped
copy using the RELENG_5_0 tag and found that src/sys/geom/geom_slice.c
does not compile.
It seems that the version of geom_slice.h which was tagged as
RELENG_5_0 is out of
In message [EMAIL PROTECTED], Craig Rodrigues writes:
Do you know what the ar: FreeBSD check1 failed error message
is caused by?
I think it is the ata-raid driver mumbling under its breath when
it doesn't find anything for it to do.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
In message [EMAIL PROTECTED], Matthew Dillon w
rites:
This commit is crashing my -current box on boot when it
goes to check for a core. I get the panic:
Negative bio_offset (-1024) on bio ...
Userland probably should not be allowed to panic the box
in that way.
Backtrace ?
In message [EMAIL PROTECTED], Matthew Dillon w
rites:
:
:In message [EMAIL PROTECTED], Matthew Dillon w
:rites:
:This commit is crashing my -current box on boot when it
:goes to check for a core. I get the panic:
:
:Negative bio_offset (-1024) on bio ...
:
:Userland probably
In message [EMAIL PROTECTED], Craig Rodrigues writes:
Hi,
I just did a cvsup and rebuilt my kernel, and now my kernel
panics upon bootup. I don't have a serial console, so I wrote
down the error messages that I saw:
I saw this one in the middle of some GEOM debug statements:
ar: FreeBSD check1
In message [EMAIL PROTECTED], Jun Kuriyama writes:
I've updated today's -current (HEAD). I got this messages after
rebooting. Is it OK?
No, it's not, but your system is almost certainly unharmed.
Fixed a second a go.
Thanks!
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL
I really wish somebody could tell us conclusively when to use
the compat geometry and when not ?
Is it only for ATA/IDE disks ?
Does it depend on the size of the disks ?
Does it also affect SCSI disks ?
Poul-Henning
In message [EMAIL PROTECTED], Takahashi Yoshihiro
writes:
The current ata
In message [EMAIL PROTECTED], Takahashi Yoshihiro
writes:
In article [EMAIL PROTECTED]
[EMAIL PROTECTED] writes:
Is it only for ATA/IDE disks ?
Does it depend on the size of the disks ?
Only for the internal IDE controller. The internal IDE controller on
pc98 uses the fixed geometry which is
In message [EMAIL PROTECTED], Johnson David writes:
On Saturday 14 December 2002 08:53 pm, Terry Lambert wrote:
The best answer out there is the majority has spoken, with
the idea being that if you are deploying on 386 hardware, you
are an embedded systems vendor, and are willing to live with
In message [EMAIL PROTECTED], Nate Lawson wri
tes:
On Sun, 15 Dec 2002, Erik Trulsson wrote:
The only remotely good reason I have heard for removing support for 386
in the default configuration is that having it in would pessimize
performance too much for more modern CPUs. How valid that
In message [EMAIL PROTECTED], walt writes:
[EMAIL PROTECTED] wrote:
Because few if any 80386 computers have the ram it takes to run sysinstall.
Was sysinstall around when 386 was new? Just curious what's changed since
then to make it bigger.
sysinstall arrived in the 486 days.
Lots of junk
In message [EMAIL PROTECTED], Alex writes:
Dear/Beste Johnson,
I read this on the advocacy list.
Tuesday, November 19, 2002, 7:56:44 PM, you wrote:
Support for the 80386 processor has been removed from the GENERIC kernel. The
default FreeBSD kernel is now more optimized for modern CPUs. No
In message [EMAIL PROTECTED], Alex writes:
I don't feel this is a good decision. (I still have a 486, act as a
small server and a 286 witch is in storage) This basally means that
any one who doesn't have the latest processor can't install FreeBSD.
No it doesn't mean that.
FreeBSD still runs
In message 006501c29d44$33a8e980$2603fb93@kloboucek, Petr Holub writes:
Hi Poul,
there's discussion in the -current list which we
had before a while. I think answer to this is
'yes' but I'm not 100% sure so I wanted to check
it with you.
Thanks very much,
Petr
[...]
I've discussed this issue
In message [EMAIL PROTECTED], Nate Lawson wri
tes:
On Fri, 6 Dec 2002 [EMAIL PROTECTED] wrote:
[...]
I've discussed this issue with Poul-Henning Kamp. You need fsck
from at least 4.7.
Is this handled by fsck/setup.c,v 1.17.2.4 commit?
Yes, this looks like the correct commit.
--
101 - 152 of 152 matches
Mail list logo
