Re: fstab weirdness / UPDATING
Yup, seems like i goofed that patch. Can you try this for me ?
Index: preen.c
===
RCS file: /home/ncvs/src/sbin/fsck/preen.c,v
retrieving revision 1.22
diff -u -r1.22 preen.c
--- preen.c 2001/03/30 08:01:34 1.22
+++ preen.c 2001/04/07 07:01:47
@@ -178,7 +178,6 @@
continue;
}
-
if (WIFEXITED(status))
retcode = WEXITSTATUS(status);
else
@@ -215,6 +214,9 @@
if (TAILQ_EMPTY(d-d_part)) {
TAILQ_REMOVE(diskh, d, d_entries);
ndisks--;
+ } else {
+ if ((ret = startdisk(d, checkit)) != 0)
+ return ret;
}
}
if (flags CHECK_DEBUG) {
--
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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: fstab weirdness / UPDATING
Date: Sat, 07 Apr 2001 09:08:41 +0200
From: Poul-Henning Kamp [EMAIL PROTECTED]
Yup, seems like i goofed that patch. Can you try this for me ?
OK; it works much better with the patch: it seems to work correctly,
from what I've tested so far.
[Below is a sketch of what I did, so folks will be able to judge how
much trust to place in the above assessment.]
* Booted -CURRENT into single-user mode. Even though this was a clean
reboot, I did a (complete) "fsck" before "mount -a", then fired up
tcsh to use as the shell for the following.
* I applied the patch from within the /urs/src/sbin/fsck directory. (Yeah,
I used -C first to make sure patch wouldn't whine too much.)
* Since the patch only affects the logic of a user-level program (vs.
the kernel, for example), I went ahead typed "make" while I was
there.
* cd /sbin mv fsck{,.save} mv /usr/obj/usr/src/sbin/fsck/fsck .
ls -l fsck*
chmod u-w fsck
* Re-boot -CURRENT, single-user mode. "fsck -p" now claims to check
each filesystem. Good.
* mount -a; things look good. Power-cycle the machine. (This is still
single-user mode, so the filesystems should merely have been marked
dirty because they're mounted, but nothing should actually have been
doing anything to them other than that.)
* Re-boot -CURRENT, single-user mode. "fsck-p" again does the usual and
expected fsck behavior -- all filesystems are checked flagged
"clean".
I like it. :-)
Thanks,
david
--
David H. Wolfskill [EMAIL PROTECTED]
As a computing professional, I believe it would be unethical for me to
advise, recommend, or support the use (save possibly for personal
amusement) of any product that is or depends on any Microsoft product.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: fstab weirdness / UPDATING
Hello everybody, I am sorry to report that the fix committed to preen.c by phk recently did not fix the problem for me entirely. I have: ad0 with partitions within s1 a through h (ad0s1a-ad0s1h) and ad1s1a. Upon rebooting (after a clean shutdown) with an up-to-date kernel and userland, all the partitons on ad0 were checked, but the ad1 was not. Yet, it was mounted r/w afterwards. I did not yet test in single-user mode though what if I say 'fsck -p'... -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
panic: lockmgr: draining against myself
doing a 'make -j16 install' on kdebase from cvs, it eventually panic'd
with:
panic: lockmgr: draining against myself
cpuid = 1; lapic.id = 0100
Debugging("panic")
CPU1 stopping CPUs: 0x0001... stopped.
Stopped at DEbuger+0x46: pushl %ebx
trace shows:
Debugger
panic
lockmgr
vop_stdlock
ufs_vnoperate
vclean
vgonel
vrecycle
ufs_inactive
ufs_vnoperate
vput
handle_workitem_freeblocks
softdep_setup_freeblocks
ffs_truncate
ufs_inactive
ufs_vnoperate
vrele
vn_close
vn_closefile
fdrop
closef
close
syscall
syscall_with_err_pushed
Based on kernel upgraded/installed on April 6th ...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: panic: lockmgr: draining against myself
just as a heads up, was just able to recreate it with a simple 'make
install' ... didn't need the -j16 to do it ...
On Sat, 7 Apr 2001, The Hermit Hacker wrote:
doing a 'make -j16 install' on kdebase from cvs, it eventually panic'd
with:
panic: lockmgr: draining against myself
cpuid = 1; lapic.id = 0100
Debugging("panic")
CPU1 stopping CPUs: 0x0001... stopped.
Stopped atDEbuger+0x46: pushl %ebx
trace shows:
Debugger
panic
lockmgr
vop_stdlock
ufs_vnoperate
vclean
vgonel
vrecycle
ufs_inactive
ufs_vnoperate
vput
handle_workitem_freeblocks
softdep_setup_freeblocks
ffs_truncate
ufs_inactive
ufs_vnoperate
vrele
vn_close
vn_closefile
fdrop
closef
close
syscall
syscall_with_err_pushed
Based on kernel upgraded/installed on April 6th ...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: panic: lockmgr: draining against myself
problem appears to be fsck related ... fsck -p was only doing two out of 6
of my file systems .. manually ran fsck on each, and right now am doing a
buildworld for last nights upgrade and we'll see what happens ...
On Sat, 7 Apr 2001, The Hermit Hacker wrote:
just as a heads up, was just able to recreate it with a simple 'make
install' ... didn't need the -j16 to do it ...
On Sat, 7 Apr 2001, The Hermit Hacker wrote:
doing a 'make -j16 install' on kdebase from cvs, it eventually panic'd
with:
panic: lockmgr: draining against myself
cpuid = 1; lapic.id = 0100
Debugging("panic")
CPU1 stopping CPUs: 0x0001... stopped.
Stopped at DEbuger+0x46: pushl %ebx
trace shows:
Debugger
panic
lockmgr
vop_stdlock
ufs_vnoperate
vclean
vgonel
vrecycle
ufs_inactive
ufs_vnoperate
vput
handle_workitem_freeblocks
softdep_setup_freeblocks
ffs_truncate
ufs_inactive
ufs_vnoperate
vrele
vn_close
vn_closefile
fdrop
closef
close
syscall
syscall_with_err_pushed
Based on kernel upgraded/installed on April 6th ...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: fstab weirdness / UPDATING
Hello, On Sat, Apr 07, 2001 at 12:04:07PM -0700, David Wolfskill wrote: I suggest "fsck -d -p" -- the debugging output could prove useful. Here we go: pass1 pass1, name /dev/ad0s1a pass2 pass2, name /dev/ad0s1f pass2, name /dev/ad0s1g pass2, name /dev/ad0s1h pass2, name /dev/ad0s1d pass2, name /dev/ad0s1e Parallel start disk /dev/ad0: ad0s1f, ad0s1g, ad0s1h, ad0s1d, ad0s1e start /tmp nowait fsck_ufs -p /dev/ad0s1f Parallel wait done ufs: /dev/ad0s1f (/tmp) 0x0 start /usr nowait fsck_ufs -p /dev/ad0s1g Parallel wait done ufs: /dev/ad0s1g (/usr) 0x0 start /usr/local nowait fsck_ufs -p /dev/ad0s1h Parallel wait done ufs: /dev/ad0s1h (/usr/local) 0x0 start /var nowait fsck_ufs -p /dev/ad0s1d Parallel wait done ufs: /dev/ad0s1d (/var) 0x0 start /var/log nowait fsck_ufs -p /dev/ad0s1e Parallel wait done ufs: /dev/ad0s1e (/var/log) 0x0 Parallel end In other words, nothing unusual, apart from the fact that ad1 is not even mentioned. If I after this say 'fsck -d -p /dev/ad1s1a', it says: start /dev/ad1s1a wait fsck_ufs -p /dev/ad1s1a and then exits, seemingly succesfully. Nothin more... if there is anything I can be helpful with, please tell me. -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: fstab weirdness / UPDATING
In message [EMAIL PROTECTED], Szilveszter Adam writ es: Hello, On Sat, Apr 07, 2001 at 12:04:07PM -0700, David Wolfskill wrote: I suggest "fsck -d -p" -- the debugging output could prove useful. Here we go: Is this with or without the patch I committed earlier today ? -- 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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
syscons panic in userconfig mode (with patch)
[ cc'd to -stable since that's affected, too ] Attempting to switch VTYs in userconfig mode will lead to a null dereference in syscons. I saw some messages about this on -current, -stable, or -bugs recently, but I can't find them now. This is pretty easy to reproduce: simply boot the kernel with the -c flag (userconfig), and press ALT+F2 (i386). As far as I can tell, this isn't a new bug. The patch is also pretty trivial. It just changes the VIRTUAL_TTY macro not to blindly assume sc-dev[x] is a valid pointer. It is safe to have it "return" NULL because any code that uses it must (and does) already check for that condition since si_tty may also be NULL in some cases (or at least that's the way I understand it). Could someone please look it over and, if it's okay, commit it? Thanks, Dima Dorfman [EMAIL PROTECTED] Index: syscons.c === RCS file: /st/src/FreeBSD/src/sys/dev/syscons/syscons.c,v retrieving revision 1.355 diff -u -r1.355 syscons.c --- syscons.c 2001/03/26 12:40:39 1.355 +++ syscons.c 2001/04/07 21:02:31 @@ -122,7 +122,8 @@ #define SC_CONSOLECTL 255 -#define VIRTUAL_TTY(sc, x) (SC_DEV((sc), (x))-si_tty) +#define VIRTUAL_TTY(sc, x) (SC_DEV((sc), (x)) != NULL ?\ + SC_DEV((sc), (x))-si_tty : NULL) static int debugger; To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
panic: spin lock sched lock ...
just panic'd, couldn't even get to the ddb prompt this time ...
panic: spin lock sched lock held by 0xcb34b840 for 5 seconds
cpuid = 1; lapic.id = 0100
Debugger("panic")
CPU1 stopping CPUs ...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
perl broken?
Different ports, similar problem:
/usr/bin/perl5 -I/usr/libdata/perl/5.6.0/mach -I/usr/libdata/perl/BSDPANIMAP.xs
IMAP.xsc mv IMAP.xsc IMAP.c
/*
* Copyright (c) 1998-2000 Carnegie Mellon University. All rights reserved.
*
* Redistribution and use in source and binar/: ?+*{} follows nothing in regexp at
IMAP.xs line 13.
*** Error code 255
Stop in /usr/ports/mail/cyrus-imapd/work/cyrus-imapd-2.0.12/perl/imap.
*** Error code 1
Stop in /usr/ports/mail/cyrus-imapd/work/cyrus-imapd-2.0.12/perl.
*** Error code 1
Stop in /usr/ports/mail/cyrus-imapd/work/cyrus-imapd-2.0.12.
*** Error code 1
Stop in /usr/ports/mail/cyrus-imapd.
*** Error code 1
Stop in /usr/ports/mail/cyrus-imapd.
/usr/bin/perl5.6.0 -I/usr/libdata/perl/5.6.0/mach -I/usr/libdata/perl/BSDPAN
Parser.xs Parser.xsc mv Parser.xsc Parser.c
Number found where operator expected at Parser.xs line 1, near "/* $Id: Parser.xs,v
2.106 2001/03"
(Missing operator before 03?)
syntax error at Parser.xs line 1, near "/* $Id: Parser.xs,v 2.106 2001/03"
Number found where operator expected at Parser.xs line 1, near "30 07"
(Missing operator before 07?)
Bareword found where operator expected at Parser.xs line 1, near "00 gisle"
(Missing operator before gisle?)
Number found where operator expected at Parser.xs line 3, near "* Copyright 1999"
(Missing operator before 1999?)
Number found where operator expected at Parser.xs line 4, near "*
Copyright 1999"
(Missing operator before 1999?)
Bareword found where operator expected at Parser.xs line 6, near "* This library"
(Missing operator before library?)
syntax error at Parser.xs line 12, near "*
* Standard"
Bareword found where operator expected at Parser.xs line 12, near "* Standard XS"
(Missing operator before XS?)
Semicolon seems to be missing at Parser.xs line 14.
String found where operator expected at Parser.xs line 15, near "extern "C""
(Do you need to predeclare extern?)
Execution of Parser.xs aborted due to compilation errors.
*** Error code 255
Stop in /usr/ports/www/p5-HTML-Parser/work/HTML-Parser-3.20.
*** Error code 1
Stop in /usr/ports/www/p5-HTML-Parser.
*** Error code 1
Stop in /usr/ports/www/p5-HTML-Parser.
*** Error code 1
--
Michael D. Harnois[EMAIL PROTECTED]
Redeemer Lutheran Church Washburn, Iowa
It is better to die excommunicated than to live
and violate the conscience. -- Thomas Aquinas
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: fstab weirdness / UPDATING *solved!*
Hello guys, [Cc-ing the list just for the sake of the archives, so that people could see what the resolution of the case was.] Thanks for trying to help me while I was busy sleeping... here I am again. As suggested, I looked at my fstab, although I do not remember fiddling with it in a long time. (In fact, the last time was when I installed my second disk into the system some time at the end of last year.) And sure as hell, there it was: next to /dev/ad1s1a there was *no* dump number and *no* pass no. Not zeros, but nothing, nada, nichts. This, of course, explains a lot of things... after putting the correct values in there, fsck worked. But I have no idea how/why the numbers got deleted... and then why it worked before? Thanks all the same, things seem to work out A OK right now. :-) -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
