Re: Missing MFC of geom_slice.c ?

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

Re: Panic during daily periodic run

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 0xc01eac

Re: Sysinstall project?

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,

Re: revoke(2) redux...

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() ?

Re: revoke(2) redux...

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 pro

Re: revoke(2) redux...

In message <[EMAIL PROTECTED]>, Garrett Wollman writes: >< 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 user has permission to open the device. If the >user somehow m

Re: Cannot open "/dev/ad0" on -CURRENT

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

Re: Cannot open "/dev/ad0" on -CURRENT

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

Re: cvs commit: src/sys/ufs/ffs ffs_vfsops.c

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 byte

Re: spec_getpages I/O read failure on md0

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 ke

Re: spec_getpages I/O read failure on md0

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. >>

Re: missed disk nodes

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 m

Re: spec_getpages I/O read failure on md0

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 t

Re: spec_getpages I/O read failure on md0

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

Re: buildworld trouble: multiple struct dos_partition.

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 ren

Re: aligned_nblks calculations broken in vm_swap.c

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.c

Re: Jail detection

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

Re: Jail detection

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 Zil

Re: panic with panic: kmem_malloc(4096): kmem_map too small...

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 actua

Re: Compilation failure on x86

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 "m

Re: panic with panic: kmem_malloc(4096): kmem_map too small...

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 d

Re: alpha tinderbox failure

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 ou

Re: VM page queue mutex not locked panic (WAS:Re: panic with panic: kmem_malloc(4096): kmem_map too small... )

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 o

Re: systat -ifstat patch

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 http://arpa

Re: systat -ifstat patch

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 [E

Re: VOP_STRATEGY on VCHR?

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), >Sorr

Re: Panic: Initiate_write_inodeblock_ufs1: already started

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

Re: specfs lock plumbing broken

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 test

Re: specfs lock plumbing broken

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

Re: gdb: failed to set signal flags properly for ast()

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() >faile

Re: Unable to mount ext2fs partition

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 part

Re: Panic: Initiate_write_inodeblock_ufs1: already started

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. >> >> Wh

Re: specfs lock plumbing broken

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 |

Re: Unable to mount ext2fs partition

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! >Abor

Re: Unable to mount ext2fs partition

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 partit

Re: VOP_STRATEGY on VCHR?

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 VC

Re: mirrored root fs?

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 ge

Re: panic with panic: kmem_malloc(4096): kmem_map too small...

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 res

Re: strange dump/restore behaviour

I've seen this when dumping live filesystems. I belive it means that dump couldn't find the file it had already dumped in the directory once it got to dump the contents. In message <[EMAIL PROTECTED]>, Dag-Erling Smorgrav writes: >This happened while copying data over to a new disk (mounted on /

Re: VOP_SPECSTRATEGY on non-VCHR

In message <[EMAIL PROTECTED]>, Lars Eggert writes: >just got this on today's -current, when accessing a mounted NTFS partition: > >VOP_SPECSTRATEGY on non-VCHR >: 0xc6d73c34: tag ntfs, type VREG, usecount 3, writecount 0, refcount 0, >flags (VV_OBJBUF), lock type ntfs: SHARED (count 1) Can you

Re: 5.0 without swap

In message <[EMAIL PROTECTED]>, "Geof frey T. Falk" writes: >Further to my previous message on encrypting swap: >In order for it to work, apparently, one must change the fstype within >the disklabel, so that the swap partition (e.g. /dev/ad0s1b) is fstype >"4.2BSD", not "swap". This shouldn't be n

Re: GEOM prevents bootblocks writing

In message <[EMAIL PROTECTED]>, Sean Kelly writes: >Since I haven't seen any response to this, I'll "me too" it in hopes that >it will get some attention drawn to it. boot0cfg and fdisk should work as advertised. There is an erratum on "disklabel -B" for 5.0-RELEASE. -- Poul-Henning Kamp

Re: FreeBSD 5.0 RC3 now available

In message <[EMAIL PROTECTED]>, "Roderick van Domburg" writes: >I would like to point to a currently unresolved issue that Thomas Moestl is >helping me solve on freebsd-sparc@. It isn't listed on the Open Issues page, >but I'd say it's something that needs to be resolved before the release is >rol

Re: Geom disklabel/fdisk issues?

In message <[EMAIL PROTECTED]>, Ju lian Elischer writes: > >I think that one of the things we need to do is declare a new flag in >disklabel that declares that the disklabel has been converted to use >relative offsets. if the flag is not set then absolute offsets are >expected.. That would give a w

Re: Geom disklabel/fdisk issues?

In message <[EMAIL PROTECTED]>, walt writes: >[EMAIL PROTECTED] wrote: >> Julian Elischer writes: >> >>>I think that one of the things we need to do is declare a new flag in >>>disklabel that declares that the disklabel has been converted to use >>>relative offsets... > >> Better plan: Abandon BS

Re: FreeBSD 5.0 RC3 now available

In message <[EMAIL PROTECTED] .com>, "local.freebsd.current" writes: >On Mon, 13 Jan 2003 11:46:43 -, [EMAIL PROTECTED] wrote: > >>In the meantime we _really_ have to ship 5.0-RELEASE, we keep >>slipping it. > >That sounds like "it's time to ship so we're going to ship". That's it. >I'm not t

Re: SMP hang at boot on Compaq Proliant ML370

In message <[EMAIL PROTECTED]>, Nicolas Kowalski writes: >Fritz Heinrichmeyer <[EMAIL PROTECTED]> writes: > >> On Wed, Jan 15, 2003 at 11:09:09AM +0100, Nicolas Kowalski wrote: >>> The server is configured for Unixware7, as told in the archives. >> >> our Compaq worked when configured for linux > >

Re: Somebody: port this: http://www.theinquirer.net/?article=7231

In message <[EMAIL PROTECTED]>, Kris Kennaway writes: > >--ALfTUftag+2gvp1h >Content-Type: text/plain; charset=us-ascii >Content-Disposition: inline > >"The tool costs $699 and Intel said it will be available in February." > >That would make it somewhat difficult, no? I don't think so. VTUNE is p

Re: panic: malloc(M_WAITOK) returned NULL

In message <[EMAIL PROTECTED]>, Kris Kennaway writes: >I just got the following on axp1: > >panic: malloc(M_WAITOK) returned NULL >db_print_backtrace() at db_print_backtrace+0x18 >panic() at panic+0x104 >malloc() at malloc+0x1a8 >initiate_write_inodeblock_ufs1() at initiate_write_inodeblock_ufs1+0

Re: HEADSUP: CCD(4) hackery...

In message <[EMAIL PROTECTED]>, Lars Eggert writes: >I just booted today's -current kernel in single-user mode to do an >installworld, and when I do the usual "ccdconfig -C" (since my /usr is >striped), I now get: > > # ccdconfig -C > ccdconfig: open: /dev/ccd0c: No such file or dire

Re: I want a sysctl kern.allow_shooting_into_my_foot!

In message <[EMAIL PROTECTED]>, Joerg Wunsch writes: >Included an old disk into a running system. Want to install a new >label onto it: > >uncle# disklabel -Brw da0 auto >disklabel: ioctl DIOCSDINFO: open partition would move or shrink > >Needless to say, there is nothing open at all on it. As i

Re: I want a sysctl kern.allow_shooting_into_my_foot!

In message <[EMAIL PROTECTED]>, Joerg Wunsch writes: >As [EMAIL PROTECTED] wrote: > >> Hang on. >> >> If no disk partitions of any kind are open, there is nothing which >> prevents you from doing a "dd if=/dev/zero of=/dev/da0 bs=64k". > >My guess is that vinum scanned the disks when starting, but

Re: I want a sysctl kern.allow_shooting_into_my_foot!

In message <[EMAIL PROTECTED]>, Joerg Wunsch writes: >It wouldn't have paniced it at all, since i /knew/ nothing was open >on it. Well, the only reason why GEOM didn't let you was that it knew that something was open. As I said, the XML output contains the truth in this matter... -- Poul-Henn

Re: I want a sysctl kern.allow_shooting_into_my_foot!

In message <[EMAIL PROTECTED]>, Bernd Walter writes: >On Tue, Jan 21, 2003 at 11:06:05PM +0100, [EMAIL PROTECTED] wrote: >> In message <[EMAIL PROTECTED]>, Joerg Wunsch writes: >> >As [EMAIL PROTECTED] wrote: >> > >> >> Hang on. >> >> >> >> If no disk partitions of any kind are open, there is noth

Re: I want a sysctl kern.allow_shooting_into_my_foot!

In message <[EMAIL PROTECTED]>, Joerg Wunsch writes: >Here's the result. What does it mean to me? (debug flag set from >DDB, and turned off in single-user again.) Here's the bug: g_dev_open(da1a, 3, 0, 0) da1a opened (FREAD|FWRITE) g_access_rel(0xc1178a40(da1a), 1, 1, 0)

Re: I want a sysctl kern.allow_shooting_into_my_foot!

In message <[EMAIL PROTECTED]>, Bernd Walter writes: >> da1a closed but without FREAD|FWRITE, which turns the close into a no-op. > >[125]cicely5# grep d_open * >grep: CVS: Operation not permitted >vinumext.h:d_open_t vinumopen; >vinumio.c: drive->lasterror = (dsw->d_open) (drive->dev, FWRITE

Re: -current error in kernel build with NO_GEOM

In message <[EMAIL PROTECTED]>, Gary Jennejohn w rites: >Am I the only person using NO_GEOM in -current? Probably. NO_GEOM is scheduled to be removed as an option in some weeks, so if there is a bug or other issue which prevents you from running GEOM this would be a really good time to tell me.

Re: GEOM & disklabel

In message <[EMAIL PROTECTED]>, Michael Reifenberger w rites: > This message is in MIME format. The first part should be readable text, > while the remaining parts are likely unreadable without MIME-aware tools. > Send mail to [EMAIL PROTECTED] for more info. > >--0-240786022-1043432225=:647 >C

Re: GEOM & disklabel

In message <[EMAIL PROTECTED]>, Michael Reifenberger writes: >On Fri, 24 Jan 2003 [EMAIL PROTECTED] wrote: >... >> Don't use the '-r' option, it gets confused because geom::BSD does >> not lie to it. >Yes, that seems to work... >Time to say good bye for '-r' ? Well, we still need it for writing t

Re: Opening /dev/tty in session leader after controlling terminal is revoked causes panic.

In message <[EMAIL PROTECTED]>, "Peter Edwards" writes: >The problem is in kern/tty_tty.c:ctty_clone. It's assuming that if the process >has its P_CONTROLT flag set, then it's session has a valid vnode for it's >controlling terminal. This doesn't hold if the terminal was revoked. Can you try this

Re: cvs commit: src/sbin/disklabel disklabel.8 disklabel.c

In message <[EMAIL PROTECTED]>, Ruslan Ermilov writes: >and installed the new kernel (without any problems) on it. Next >reboot refused to boot FreeBSD by mentioning that "No operating >system was found". I wondered how I managed to screw my disk up. Welcome to the club if people who was bitten

Re: HEADSUP: disklabel(8): men at work.

In message <[EMAIL PROTECTED]>, Wilko Bulte writes: >On Sun, Jan 26, 2003 at 03:47:11PM +0100, Poul-Henning Kamp wrote: >> >> I'm still not done with disklabel(8), and I have not run it through >> all the tests I want (I'm waiting for my glacial 233MHz EV45 alpha >> to compile a world) so be caref

Re: alpha/GENERIC børked

In message <[EMAIL PROTECTED]>, Poul-Henning Kamp writes: > ># make >cc -c -O -pipe -mcpu=ev4 -mtune=ev5 -Wall -Wredundant-decls -Wnested-externs >-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual >-fformat-extensions -ansi -g -nostdinc -I- -I. -I../../.. -I../../..

Re: mdconfig -l broken after /sys/dev/md/md.c rev 1.77

In message <[EMAIL PROTECTED]>, Giorgos Keramidas writes: >mdconfig -l stopped working in -current after revision 1.76 of md.c. > >I just reverted src/sys/dev/md/md.c to revision 1.76 and removed >M_WAITOK to let me build a kernel with that version of md.c. Now >mdconfig correctly lists the open m

Re: Am I blind? (devfs issue)

In message <[EMAIL PROTECTED]>, "Thomas E. Zander" write s: >Sorry, this is probably a stupid question, but: > >[riggs] ~ > ll /dev/ds* >crw-rw-rw- 1 root wheel 30, 3 27 Jan 14:46 /dev/dsp0.0 >crw-rw-rw- 1 root wheel 30, 0x00010003 27 Jan 10:59 /dev/dsp0.1 >crw-rw-rw- 1 root wheel 30,

Re: Opening /dev/tty in session leader after controlling terminal is revoked causes panic.

In message <[EMAIL PROTECTED]>, "Peter Edwards" writes: >> >The problem is in kern/tty_tty.c:ctty_clone. It's assuming that if the process >> >has its P_CONTROLT flag set, then it's session has a valid vnode for it's >> >controlling terminal. This doesn't hold if the terminal was revoked. >Yes, t

Re: VOP_STRATEGY on VCHR

In message <[EMAIL PROTECTED]>, Enache Adrian writes: >I get this when I try to access for the first time a file on an ext2fs >filesystem. > >VOP_STRATEGY on VCHR Please try this patch and let me know if it helps ? Index: ext2_vnops.c ==

Re: last KSE changes

In message <[EMAIL PROTECTED]>, Jul ian Elischer writes: >The rumour mill has been running wild on this but **AS FAR AS I KNOW** >the breakages have been fixed, since no-one has told me directl of any >current breakages. If you have any breakage from this commit, >PLEASE TELL ME! I think you sho

Re: ata0: resetting device - ASUS P4S8X

In message <[EMAIL PROTECTED]>, Christoph Kuk ulies writes: > >I bought new hardware for a server today, an ASUS P4S8X with >an 1.8 GHZ P4 CPU, nothing fancy I would say, which has an >onboard RAID controller (Promise) but I'm not using it >for the moment. I attached an IBM 60GB Deskstar ATA/IDE di

Re: split out patch

In message <[EMAIL PROTECTED]>, Ju lian Elischer writes: >still no comments? Julian, you sent this out a few hours ago, after people had spent a lot of time and getting quite frustrated trying to get you to DTRT with your mentee's inappropriate commit. If people are sick and tired of you right n

Re: split out patch

In message <[EMAIL PROTECTED]>, Ju lian Elischer writes: >Oh shut up Poul-Henning. Try to remain civil here Julian :-) I tried to explain the situation to you, to make sure you would not be tempted to do rush something which needs to take the time things take. >I know I'm on your shit list, an

Re: rand() is broken

In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes: > >--SUOF0GtieIMvvwua >Content-Type: text/plain; charset=us-ascii >Content-Disposition: inline >Content-Transfer-Encoding: quoted-printable > >On Sun, Feb 02, 2003 at 01:11:06 -0800, Kris Kennaway wrote: >>=20 >> Another problem (noticed b

Re: rand() is broken

In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes: >On Sun, Feb 02, 2003 at 17:30:48 +, Mark Murray wrote: >> >> Why not? Arc4 is a) deterministic and b) good for all bits. > >If you mean arc4random() function - not, because it use true randomness, >if you mean RC4 algorithm, probably

Re: rand() is broken

In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes: >On Sun, Feb 02, 2003 at 19:32:50 +0100, [EMAIL PROTECTED] wrote: >> >> Anyway, last time we discussed this, I think we stuck with the rand() >> we had because we feared that people were using it's repeatable well >> documented sequence o

Re: rand() is broken

In message <[EMAIL PROTECTED]>, Mark Murray wr ites: >We have most of this, and RC4 can deliver. RC4's "licence" is >fine. Call it "ArCFour" and there is no problem. The code is >small, fast and repeatable, and meets conditions 1-4 above. There are some concerns about RC4's strength and predictab

Re: gbde & vnode md devices?

In message <[EMAIL PROTECTED]>, Darryl Okahata writes : >su-2.05b# gbde init /dev/md0 -L /tmp/foo.lock Don't use the -L and -l arguments unless you have to. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD sinc

Re: gbde & vnode md devices?

In message <[EMAIL PROTECTED]>, Darryl Okahata writes : >[EMAIL PROTECTED] wrote: > >> >su-2.05b# gbde init /dev/md0 -L /tmp/foo.lock >> >> Don't use the -L and -l arguments unless you have to. > > Thanks, but that was what I originally tried, and I still got the >"gbde: ioctl(GEOMCONFIGGEOM):

Re: gbde & vnode md devices?

In message <[EMAIL PROTECTED]>, Darryl Okahata writes : >[EMAIL PROTECTED] wrote: > >> Can you please try this: >> >> mdconfig -a -t malloc -s 4m -u 75 >> gbde init /dev/md75 >> gbde attach md75 > > Nope, exact same error. That is weird, it works like a charm here. syv

Re: gbde & vnode md devices?

In message <[EMAIL PROTECTED]>, Darryl Okahata writes : >[EMAIL PROTECTED] wrote: > >> Say, do you actually have the GEOM_BDE option in your kernel ? > > Sigh, no. I missed it in gbde(4). > > You might want to further idiot-proof gbde(8) with code like: > >err(1, "ioctl(GEOMCONFIGGEOM) (is

Re: extended slices on 5.0-RELEASE?

In message <[EMAIL PROTECTED]>, Mike Meyer writes: >[I asked this on -questions, and got no response, so...] > >Is it just me, or has disklabel lost the ability to read/write from >extended slices in 5.0-RELEASE? I hope not. Please send me the output of sysctl -b kern.geom.confxml in priv

Re: Minor oddity with sysinstall/disklabel on -current

In message , Garance A Drosihn writes: >So, I'm trying something on -current. > >I boot up, log into root. I have two hard disks on the system. All >of my mounted partitions are on ad0, except for one partition on ad2. >I 'umount' that partition. I run the

Re: Preview: GEOMs statistics code.

In message , Brad Knowles writes: >At 10:44 PM +0100 2003/02/04, Poul-Henning Kamp wrote: > >> In difference from the devstat framework which measures how big a >> percentage of the time a drive has one or more outstanding requests, >> I think that measurin

Re: Preview: GEOMs statistics code.

In message <[EMAIL PROTECTED]>, "Greg 'groggy' Lehey" writes: >2. %busy. I personally think this is the most important one, but as >you say, there's no reason not to do the others as well. The problem with this one is that we can't measure it in a way which tells us the truth, and we may n

Re: Preview: GEOMs statistics code.

In message , Brad Knowles writes: >At 8:26 AM +0100 2003/02/05, [EMAIL PROTECTED] wrote: > My understanding was that a disk is 100% busy, if the heads are >constantly moving to and fro, and there is no period of time when >they aren't being yanked around.

Re: Wrong date for DEVFS entries

In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes: >Look at the snapshot below, taken right after boot time. Most entries are >at "Feb 5 22:34" which is boot time, but some other are "Feb 6 01:34" >which is in the future! It looks like TZ offset added for them by mistake. >Please fix thi

Re: 5.0 issues

In message <[EMAIL PROTECTED]>, Oliver Fromme writes : >1. I have some shell scripts that make use of redirections >with file descriptors (3>&1 and /dev/fd/3 etc.). Those >worked under 4.x out of the box, but didn't work in 5.0, >because there is no /dev/fd/3 in DEVFS. I solved this by >manuall

Re: Wrong date for DEVFS entries

In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes: >On Wed, Feb 05, 2003 at 20:52:54 +0100, [EMAIL PROTECTED] wrote: >> >> My guess: Your RTC has the wrong time and ntpdate or similar stepped >> your clock to be correct. > >It is each boot repeated effect, not one time. >I run local cloc

Re: Wrong date for DEVFS entries

In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes: >On Wed, Feb 05, 2003 at 22:10:41 +0100, [EMAIL PROTECTED] wrote: >> >> You can try this patch instead. It has a different side effect: >> if you reset your clock the (untouched) timestamps will change. > >It not helps, see 00:48 -> 03:4

Re: Wrong date for DEVFS entries

In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes: >On Wed, Feb 05, 2003 at 23:23:26 +0100, [EMAIL PROTECTED] wrote: >> >> Try to remove the three "fix" lines, and see what you get then. >> > >Very strange effect: 3 kinds of entries appearse: >1) Jan 1 1970 These are the intact untouc

Re: Wrong date for DEVFS entries

In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes: >On Wed, Feb 05, 2003 at 23:44:08 +0100, [EMAIL PROTECTED] wrote: >> >> >2) Feb 6 01:36 (boot time) >> >3) Feb 6 04:36 (+3 TZ future jump) >> >> These timestamps have been touched, and the clock has made a 3 hour >> jump either forward

Re: Wrong date for DEVFS entries

In message <[EMAIL PROTECTED]>, Bruce Evans writes: >On Thu, 6 Feb 2003, Andrey A. Chernov wrote: > >> On Wed, Feb 05, 2003 at 23:44:08 +0100, [EMAIL PROTECTED] wrote: >> > >> > >2) Feb 6 01:36 (boot time) >> > >3) Feb 6 04:36 (+3 TZ future jump) >> > >> > These timestamps have been touched, and

Re: Wrong date for DEVFS entries

In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes: >> This is not any different from any other filesystem. > >No, it IS different - no real filesystems mounted at this point yet, so no >real timestamps damaged. Think diskless NFS, think MD(4) based root, think... The only problem is

Re: GEOM and Extended Slices

In message <[EMAIL PROTECTED]>, Hiten Pandya writes: >Hi gang. > >Recently removing the NO_GEOM option from my kernel; I noticed that my >dos extended slices dev entries disappeared under a GEOM kernel. This >is sorta bad, but I can bare for now. > >Also, I tried searching the sys/geom/ tree if th

Re: Wrong date for DEVFS entries

In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes: >On Thu, Feb 06, 2003 at 22:10:43 +1100, Bruce Evans wrote: >> >> More precisely: some are mounted, but they are mounted read-only (modulo >> the bug that adjkerntz is run a little after mounting filesystems read-write). > >Obvious workar

Re: Wrong date for DEVFS entries

In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes: >On Sat, Feb 08, 2003 at 00:16:24 +0100, [EMAIL PROTECTED] wrote: >> >> Can we stop considering workarounds, and instead work on solving >> the problem please ? > >I see no solving way until kernel will understand fully and can handle >ti

Re: Preview: GEOMs statistics code.

I have played with the statistics collection in GEOM a bit, and need more feedback, but first: try to play with it a bit. Assuming you're running -current as of today, otherwise install include files and libgeom by hand first. Apply this patch in src/sys/geom and make a new kernel. http

Re: Do we still have a FIFO / named pipe problem?

Yes, we do have FIFO/named pipe problems in -current. I committed a workaround to prevent one particular condition under which my diskless box would hang forever in sendmail processing in /etc/rc by setting a 1 sec timeout on the sleep it hung in. This is nowhere near correct as pointed out by B

Re: Does bg fsck have problems with large filesystems?

In message <[EMAIL PROTECTED]>, Gerrit =?iso-8859-1?Q? K=FChn?= writes: >On Tue, Jan 28, 2003 at 06:31:42PM +0100, Gerrit Kühn wrote: > >> > I've been trying to reproduce this bug on my desktop. This machine has 2 >> > 80gb disks, one of which is dedicated with one slice. So far, after 8 hard >> >

Re: Preview: GEOMs statistics code.

In message <[EMAIL PROTECTED]>, Mattias Pantzare writes: >[EMAIL PROTECTED] wrote: >> I have played with the statistics collection in GEOM a bit, and need >> more feedback, but first: try to play with it a bit. >> >> Assuming you're running -current as of today, otherwise install >> include files

Re: panic with heavy io

In message <[EMAIL PROTECTED]>, Mark Santcroos writes: >While doing heavy IO (updating my p4 repo) on my laptop I got the following >panic. (I was running in X so both backtrace and dmesg are from the core >dump after reboot) > >I'm wondering whether the ENOMEM's reported by GEOM point out that GE

  1   2   >