From owner-freebsd-fs Mon Dec 4 13:19:29 2000
From owner-freebsd-fs@FreeBSD.ORG Mon Dec 4 13:19:22 2000
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11])
by hub.freebsd.org (Postfix) with SMTP id CAAE937B400
for <freebsd-fs@freebsd.org>; Mon, 4 Dec 2000 13:19:21 -0800 (PST)
Received: from gosset.maths.tcd.ie by salmon.maths.tcd.ie with SMTP
id <aa25259@salmon>; 4 Dec 2000 21:19:20 +0000 (GMT)
To: freebsd-fs@freebsd.org
Cc: iedowse@maths.tcd.ie, Kirk McKusick <mckusick@mckusick.com>
Subject: SIGINFO handler for fsck(8)
Date: Mon, 04 Dec 2000 21:19:19 +0000
From: Ian Dowse <iedowse@maths.tcd.ie>
Message-ID: <200012042119.aa25259@salmon.maths.tcd.ie>
Sender: owner-freebsd-fs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
I've had this patch lying around here for a while - it adds a simple
SIGINFO handler to fsck(8) so you can tell what it's doing by
pressing Ctrl-T. The output will be something like:
^T
load: 0.14 cmd: fsck_ufs 10473 [physstr] 2.12u 0.30s 8% 2016k
/dev/da0s1f: phase 1: cyl group 26 of 60 (43%)
^T
load: 0.12 cmd: fsck_ufs 10473 [physstr] 4.00u 0.49s 11% 2804k
/dev/da0s1f: phase 2: dir 488 of 27965 (1%)
Is this a feature we want in fsck? It doesn't really help except
to give you something to do while waiting for a huge filesystem to
be checked :-) I guess it also allows you to see if fsck is actually
getting anywhere.
Ian
Index: fsck.h
===================================================================
RCS file: /FreeBSD/FreeBSD-CVS/src/sbin/fsck_ffs/fsck.h,v
retrieving revision 1.14
diff -u -r1.14 fsck.h
--- fsck.h 2000/10/09 08:26:28 1.14
+++ fsck.h 2000/12/04 21:06:19
@@ -223,6 +223,8 @@
ufs_daddr_t n_blks; /* number of blocks in use */
ufs_daddr_t n_files; /* number of files in use */
+int got_siginfo; /* received a SIGINFO */
+
#define clearinode(dp) (*(dp) = zino)
struct dinode zino;
@@ -280,6 +282,7 @@
struct dinode *getnextinode __P((ino_t inumber));
void getpathname __P((char *namebuf, ino_t curdir, ino_t ino));
struct dinode *ginode __P((ino_t inumber));
+void infohandler __P((int sig));
void inocleanup __P((void));
void inodirty __P((void));
struct inostat *inoinfo __P((ino_t inum));
Index: main.c
===================================================================
RCS file: /FreeBSD/FreeBSD-CVS/src/sbin/fsck_ffs/main.c,v
retrieving revision 1.22
diff -u -r1.22 main.c
--- main.c 2000/10/09 08:26:28 1.22
+++ main.c 2000/12/04 21:06:19
@@ -140,6 +140,7 @@
(void)signal(SIGINT, catch);
if (preen)
(void)signal(SIGQUIT, catchquit);
+ signal(SIGINFO, infohandler);
/*
* Push up our allowed memory limit so we can cope
* with huge filesystems.
Index: pass1.c
===================================================================
RCS file: /FreeBSD/FreeBSD-CVS/src/sbin/fsck_ffs/pass1.c,v
retrieving revision 1.18
diff -u -r1.18 pass1.c
--- pass1.c 2000/07/12 06:19:22 1.18
+++ pass1.c 2000/12/04 21:06:19
@@ -89,6 +89,13 @@
inumber = c * sblock.fs_ipg;
setinodebuf(inumber);
inosused = sblock.fs_ipg;
+
+ if (got_siginfo) {
+ printf("%s: phase 1: cyl group %d of %d (%d%%)\n",
+ cdevname, c, sblock.fs_ncg,
+ c * 100 / sblock.fs_ncg);
+ got_siginfo = 0;
+ }
/*
* If we are using soft updates, then we can trust the
* cylinder group inode allocation maps to tell us which
Index: pass1b.c
===================================================================
RCS file: /FreeBSD/FreeBSD-CVS/src/sbin/fsck_ffs/pass1b.c,v
retrieving revision 1.7
diff -u -r1.7 pass1b.c
--- pass1b.c 1999/08/28 00:12:46 1.7
+++ pass1b.c 2000/12/04 21:06:19
@@ -65,6 +65,12 @@
duphead = duplist;
inumber = 0;
for (c = 0; c < sblock.fs_ncg; c++) {
+ if (got_siginfo) {
+ printf("%s: phase 1c: cyl group %d of %d (%d%%)\n",
+ cdevname, c, sblock.fs_ncg,
+ c * 100 / sblock.fs_ncg);
+ got_siginfo = 0;
+ }
for (i = 0; i < sblock.fs_ipg; i++, inumber++) {
if (inumber < ROOTINO)
continue;
Index: pass2.c
===================================================================
RCS file: /FreeBSD/FreeBSD-CVS/src/sbin/fsck_ffs/pass2.c,v
retrieving revision 1.10
diff -u -r1.10 pass2.c
--- pass2.c 1999/08/28 00:12:46 1.10
+++ pass2.c 2000/12/04 21:06:19
@@ -134,6 +134,12 @@
dp = &dino;
inpend = &inpsort[inplast];
for (inpp = inpsort; inpp < inpend; inpp++) {
+ if (got_siginfo) {
+ printf("%s: phase 2: dir %d of %d (%d%%)\n", cdevname,
+ inpp - inpsort, inplast, (inpp - inpsort) * 100 /
+ inplast);
+ got_siginfo = 0;
+ }
inp = *inpp;
if (inp->i_isize == 0)
continue;
Index: pass3.c
===================================================================
RCS file: /FreeBSD/FreeBSD-CVS/src/sbin/fsck_ffs/pass3.c,v
retrieving revision 1.7
diff -u -r1.7 pass3.c
--- pass3.c 1999/08/28 00:12:47 1.7
+++ pass3.c 2000/12/04 21:06:20
@@ -59,6 +59,12 @@
char namebuf[MAXNAMLEN+1];
for (inpindex = inplast - 1; inpindex >= 0; inpindex--) {
+ if (got_siginfo) {
+ printf("%s: phase 3: dir %d of %d (%d%%)\n", cdevname,
+ inplast - inpindex, inplast,
+ 100 - inpindex * 100 / inplast);
+ got_siginfo = 0;
+ }
inp = inpsort[inpindex];
state = inoinfo(inp->i_number)->ino_state;
if (inp->i_number == ROOTINO ||
Index: pass4.c
===================================================================
RCS file: /FreeBSD/FreeBSD-CVS/src/sbin/fsck_ffs/pass4.c,v
retrieving revision 1.7
diff -u -r1.7 pass4.c
--- pass4.c 1999/08/28 00:12:47 1.7
+++ pass4.c 2000/12/04 21:06:20
@@ -62,6 +62,12 @@
idesc.id_type = ADDR;
idesc.id_func = pass4check;
for (cg = 0; cg < sblock.fs_ncg; cg++) {
+ if (got_siginfo) {
+ printf("%s: phase 4: cyl group %d of %d (%d%%)\n",
+ cdevname, cg, sblock.fs_ncg,
+ cg * 100 / sblock.fs_ncg);
+ got_siginfo = 0;
+ }
inumber = cg * sblock.fs_ipg;
for (i = 0; i < inostathead[cg].il_numalloced; i++, inumber++) {
if (inumber < ROOTINO)
Index: pass5.c
===================================================================
RCS file: /FreeBSD/FreeBSD-CVS/src/sbin/fsck_ffs/pass5.c,v
retrieving revision 1.18
diff -u -r1.18 pass5.c
--- pass5.c 2000/07/06 02:03:11 1.18
+++ pass5.c 2000/12/04 21:06:20
@@ -169,6 +169,12 @@
for (i = fs->fs_size; i < j; i++)
setbmap(i);
for (c = 0; c < fs->fs_ncg; c++) {
+ if (got_siginfo) {
+ printf("%s: phase 5: cyl group %d of %d (%d%%)\n",
+ cdevname, c, sblock.fs_ncg,
+ c * 100 / sblock.fs_ncg);
+ got_siginfo = 0;
+ }
getblk(&cgblk, cgtod(fs, c), fs->fs_cgsize);
if (!cg_chkmagic(cg))
pfatal("CG %d: BAD MAGIC NUMBER\n", c);
Index: utilities.c
===================================================================
RCS file: /FreeBSD/FreeBSD-CVS/src/sbin/fsck_ffs/utilities.c,v
retrieving revision 1.14
diff -u -r1.14 utilities.c
--- utilities.c 2000/10/09 09:21:04 1.14
+++ utilities.c 2000/12/04 21:07:20
@@ -101,3 +101,10 @@
*/
return (origname);
}
+
+void
+infohandler(sig)
+ int sig;
+{
+ got_siginfo = 1;
+}
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message
From owner-freebsd-fs Mon Dec 4 14:15:37 2000
From owner-freebsd-fs@FreeBSD.ORG Mon Dec 4 14:15:35 2000
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20])
by hub.freebsd.org (Postfix) with ESMTP id 63C4F37B400
for <freebsd-fs@FreeBSD.ORG>; Mon, 4 Dec 2000 14:15:35 -0800 (PST)
Received: (from bright@localhost)
by fw.wintelcom.net (8.10.0/8.10.0) id eB4MFSZ18699;
Mon, 4 Dec 2000 14:15:28 -0800 (PST)
Date: Mon, 4 Dec 2000 14:15:28 -0800
From: Alfred Perlstein <bright@wintelcom.net>
To: Ian Dowse <iedowse@maths.tcd.ie>
Cc: freebsd-fs@FreeBSD.ORG, Kirk McKusick <mckusick@mckusick.com>
Subject: Re: SIGINFO handler for fsck(8)
Message-ID: <20001204141528.Z8051@fw.wintelcom.net>
References: <200012042119.aa25259@salmon.maths.tcd.ie>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <200012042119.aa25259@salmon.maths.tcd.ie>; from iedowse@maths.tcd.ie on Mon, Dec 04, 2000 at 09:19:19PM +0000
Sender: bright@fw.wintelcom.net
Sender: owner-freebsd-fs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
* Ian Dowse <iedowse@maths.tcd.ie> [001204 13:19] wrote:
>
> I've had this patch lying around here for a while - it adds a simple
> SIGINFO handler to fsck(8) so you can tell what it's doing by
> pressing Ctrl-T. The output will be something like:
>
> ^T
> load: 0.14 cmd: fsck_ufs 10473 [physstr] 2.12u 0.30s 8% 2016k
> /dev/da0s1f: phase 1: cyl group 26 of 60 (43%)
> ^T
> load: 0.12 cmd: fsck_ufs 10473 [physstr] 4.00u 0.49s 11% 2804k
> /dev/da0s1f: phase 2: dir 488 of 27965 (1%)
>
> Is this a feature we want in fsck? It doesn't really help except
> to give you something to do while waiting for a huge filesystem to
> be checked :-) I guess it also allows you to see if fsck is actually
> getting anywhere.
I really like this, it would be nice to have an option for fsck to
display the progress without the signals though, the only difficulty
would be when it's doing parrallel fscks of several filesystems,
but you could have the children talk to the parent who would then
format the data for output.
-Alfred
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message
From owner-freebsd-fs Tue Dec 5 2:21:30 2000
From owner-freebsd-fs@FreeBSD.ORG Tue Dec 5 02:21:29 2000
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from MX.il.xosoft.com (unknown [62.68.192.66])
by hub.freebsd.org (Postfix) with ESMTP id 5B8CD37B400
for <freebsd-fs@FreeBSD.ORG>; Tue, 5 Dec 2000 02:21:28 -0800 (PST)
Received: from xosoft.com ([10.10.1.93])
by MX.il.xosoft.com (Lotus Domino Release 5.0.5)
with ESMTP id 2000120512212442:501 ;
Tue, 5 Dec 2000 12:21:24 +0200
Message-ID: <3A2CC0FF.79EEB4FB@xosoft.com>
Date: Tue, 05 Dec 2000 12:18:40 +0200
From: Ilya Usvyatsky <ilya@xosoft.com>
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en,ru
MIME-Version: 1.0
To: FreeBSD-FS Mailing List <freebsd-fs@FreeBSD.ORG>
Subject: VFCF_LOOPBACK flag
X-MIMETrack: Itemize by SMTP Server on MX/XOSoft(Release 5.0.5 |September 22, 2000) at
12/05/2000 12:21:24 PM,
Serialize by Router on MX/XOSoft(Release 5.0.5 |September 22, 2000) at 12/05/2000
12:21:28 PM,
Serialize complete at 12/05/2000 12:21:28 PM
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-fs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Hi ppl,
I am implementing (actually, porting from Solaris) now some
special-purpose stackable file system.
This FS stacks transparently over existing sub-tree of any 'real' FS and
provides some special
functionality via ioctl() calls.
Here is a question that arised to me regarding the VFCF_LOOPBACK flag.
The comment in <sys/mount.h> states that this flag means that the FS is
aliasing some other one.
On the other hand, in my case no aliasing is done (since I'm mounting
transparently and do not
create new name space). So, should I specify the flag in VFS_SET()
macro?
Any hints will be greatly appretiated.
Thank you in advance,
sincerely,
Ilya.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message
From owner-freebsd-fs Tue Dec 5 2:40:42 2000
From owner-freebsd-fs@FreeBSD.ORG Tue Dec 5 02:40:39 2000
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133])
by hub.freebsd.org (Postfix) with ESMTP id 071EE37B404
for <freebsd-fs@FreeBSD.ORG>; Tue, 5 Dec 2000 02:40:38 -0800 (PST)
Received: (from daemon@localhost)
by smtp03.primenet.com (8.9.3/8.9.3) id DAA09867;
Tue, 5 Dec 2000 03:38:22 -0700 (MST)
Received: from usr05.primenet.com(206.165.6.205)
via SMTP by smtp03.primenet.com, id smtpdAAAkjaaot; Tue Dec 5 03:38:10 2000
Received: (from tlambert@localhost)
by usr05.primenet.com (8.8.5/8.8.5) id DAA27828;
Tue, 5 Dec 2000 03:40:20 -0700 (MST)
From: Terry Lambert <tlambert@primenet.com>
Message-Id: <200012051040.DAA27828@usr05.primenet.com>
Subject: Re: VFCF_LOOPBACK flag
To: ilya@xosoft.com (Ilya Usvyatsky)
Date: Tue, 5 Dec 2000 10:40:20 +0000 (GMT)
Cc: freebsd-fs@FreeBSD.ORG (FreeBSD-FS Mailing List)
In-Reply-To: <3A2CC0FF.79EEB4FB@xosoft.com> from "Ilya Usvyatsky" at Dec 05, 2000 12:18:40 PM
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: tlambert@usr05.primenet.com
Sender: owner-freebsd-fs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
> Hi ppl,
> I am implementing (actually, porting from Solaris) now some
> special-purpose stackable file system.
> This FS stacks transparently over existing sub-tree of any 'real' FS and
> provides some special
> functionality via ioctl() calls.
> Here is a question that arised to me regarding the VFCF_LOOPBACK flag.
> The comment in <sys/mount.h> states that this flag means that the FS is
> aliasing some other one.
> On the other hand, in my case no aliasing is done (since I'm mounting
> transparently and do not
> create new name space). So, should I specify the flag in VFS_SET()
> macro?
The flags should be set.
The need for the flag is the result of the fact that the vnode
object in each VFS layer will, by definition, have its own
vmobject_t, which means that the cache coherency has to be
explicit, rather than being assumed as a result of the VM and
buffer cache unification.
See the NULLFS code changes with regart to VOP_{GET|PUT}PAGES(),
since this flag doesn't really work like it's supposed to work.
Really, the upper level paging code wants to operate against the
loweset level backing object before a translation, proxy, or
other operation which means that the backing object pages aren't
laid out the same as the underlying vnode in an inferior stack.
But set it anyway, incase this is ever fixed.
Terry Lambert
terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message
From owner-freebsd-fs Tue Dec 5 8:41:25 2000
From owner-freebsd-fs@FreeBSD.ORG Tue Dec 5 08:41:23 2000
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from chuggalug.clues.com (chuggalug.clues.com [194.159.1.85])
by hub.freebsd.org (Postfix) with ESMTP id B7F1237B400
for <fs@freebsd.org>; Tue, 5 Dec 2000 08:41:22 -0800 (PST)
Received: (from geoffb@localhost)
by chuggalug.clues.com (8.9.3/8.9.3) id QAA31718
for fs@freebsd.org; Tue, 5 Dec 2000 16:48:52 GMT
(envelope-from geoffb)
Date: Tue, 5 Dec 2000 16:48:52 +0000
From: Geoff Buckingham <geoffb@chuggalug.clues.com>
To: fs@freebsd.org
Subject: GFS interest?
Message-ID: <20001205164852.A30962@chuggalug.clues.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
Sender: owner-freebsd-fs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Does anyone else have an interest in the apparently now stalled freebsd
port of GFS.
The gfs-devel lists seem to indicate the port was being done by an individual
who left the project after doing the majority of the abstraction for the
port. (Could be way of here as only greped the mail archive.)
outline:
http://www.sistina.com/gfs/pubs/usenix1999.pdf
Sadly, this is of course all under the gpl.
--
GeoffB
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message
From owner-freebsd-fs Tue Dec 5 15:55: 6 2000
From owner-freebsd-fs@FreeBSD.ORG Tue Dec 5 15:55:05 2000
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from beastie.mckusick.com (tserver.conference.usenix.org [209.179.127.3])
by hub.freebsd.org (Postfix) with ESMTP id 7FB7037B400
for <freebsd-fs@freebsd.org>; Tue, 5 Dec 2000 15:55:04 -0800 (PST)
Received: from beastie.mckusick.com (localhost [127.0.0.1])
by beastie.mckusick.com (8.9.3/8.9.3) with ESMTP id GAA10110;
Tue, 5 Dec 2000 06:45:26 -0800 (PST)
(envelope-from mckusick@beastie.mckusick.com)
Message-Id: <200012051445.GAA10110@beastie.mckusick.com>
To: Ian Dowse <iedowse@maths.tcd.ie>
Subject: Re: SIGINFO handler for fsck(8)
Cc: freebsd-fs@freebsd.org
In-Reply-To: Your message of "Mon, 04 Dec 2000 21:19:19 GMT."
<200012042119.aa25259@salmon.maths.tcd.ie>
Date: Tue, 05 Dec 2000 06:45:26 -0800
From: Kirk McKusick <mckusick@mckusick.com>
Sender: owner-freebsd-fs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
To: freebsd-fs@freebsd.org
cc: iedowse@maths.tcd.ie, Kirk McKusick <mckusick@mckusick.com>
Subject: SIGINFO handler for fsck(8)
Date: Mon, 04 Dec 2000 21:19:19 +0000
From: Ian Dowse <iedowse@maths.tcd.ie>
I've had this patch lying around here for a while - it adds a simple
SIGINFO handler to fsck(8) so you can tell what it's doing by
pressing Ctrl-T. The output will be something like:
^T
load: 0.14 cmd: fsck_ufs 10473 [physstr] 2.12u 0.30s 8% 2016k
/dev/da0s1f: phase 1: cyl group 26 of 60 (43%)
^T
load: 0.12 cmd: fsck_ufs 10473 [physstr] 4.00u 0.49s 11% 2804k
/dev/da0s1f: phase 2: dir 488 of 27965 (1%)
Is this a feature we want in fsck? It doesn't really help except
to give you something to do while waiting for a huge filesystem to
be checked :-) I guess it also allows you to see if fsck is actually
getting anywhere.
Ian
Looks like a good idea to me. I am happy to have you commit it.
Kirk
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message
From owner-freebsd-fs Tue Dec 5 21:25:13 2000
From owner-freebsd-fs@FreeBSD.ORG Tue Dec 5 21:25:07 2000
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mail.iconz.co.nz (etrn.iconz.co.nz [210.48.22.36])
by hub.freebsd.org (Postfix) with ESMTP
id 4A46837B69C; Tue, 5 Dec 2000 21:24:56 -0800 (PST)
Received: from creativejuice.co.nz (ip-210-48-60-242.iconz.net.nz [210.48.60.242] (may be forged))
by mail.iconz.co.nz (8.9.3/8.9.3) with ESMTP id SAA043700976080139;
Wed, 6 Dec 2000 18:22:19 +1300 (NZDT)
From: tom@aba.com
Message-Id: <200012060522.SAA043700976080139@mail.iconz.co.nz>
Received: from [62.159.146.73] by [192.168.1.2]
with SMTP (QuickMail Pro Server for Mac 2.0.1); 06-Dec-2000 18:23:08 +1300
To: <Undisclosed.Recipients@mail.iconz.co.nz>
Subject: Search Engine Optimization Kit-2001 24123
Date: Wed, 06 Dec 2000 00:16:29 -0500
MIME-Version: 1.0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 1
X-MSMail-Priority: High
Errors-To:
X-Mailer: Outlook Express
X-Originating-IP:
Sender: owner-freebsd-fs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
<HTML>
<BODY>
<TABLE CELLPADDING=3D"10" WIDTH=3D"80%" BGCOLOR=3D"#9dcaf7" BORDER=3D"5">
<TBODY>
<TR>
<TD><FONT FACE=3D"Arial Black">Get Top 10 Positions With The Search
Engine Optimization Kit-2001
<br><br>
No hype ... no gimmicks ... just the facts ... and only $59! <BR>
</FONT></TD>
</TR>
<TR>
<TD><FONT FACE=3D"Times New Roman"><BR>
<B>Hello Friend,</B> <BR>
<BR>
We created the<B> Search Engine Optimization
Kit-2001</B> to achieve high positions in search engines. This unique
<B>Kit</B> includes: </FONT><UL>
<LI><B>Detailed information</B> about how search engines work,<BR>
<BR>
</LI>
<LI><B>Step-by-step instructions</B> to create, high-ranking,"search-=
engine-friendly" pages, <BR>
<BR>
</LI>
<LI><B>All the tools and resources</B> you need to create pages, submit to=
engines and track your placements, and <BR>
<BR>
</LI>
<LI><B>Ongoing personal support</B> by email and phone. <BR>
<BR>
</LI>
</UL>
<b>Click to receive
<A HREF=3D"mailto:seok21@libero.it?Subject=3DFree Information 101">Free In=
formation
about Search Engines and the Kit</A>, or call direct to 937-640-2762. </b>
<br><br>
We reply promptly to all inquires. <BR>
<BR>
<B>Dr. Jerry R. Perrich, Director<BR>
The Internet Marketing Institute, Inc.<BR>
<I>Helping You Be Successful Online</I><BR>
937-640-2762<BR>
</B><BR>
<BR>
PS - Please forward this email to any of your business associates or
friends who may benefit from it. <BR>
<BR>
</TD>
</TR>
<TR>
<TD><FONT FACE=3D"Times New Roman" SIZE=3D"-1"><B>REMOVAL INSTRUCTIONS</B>=
<BR>
Per federal legislation, you can be removed from this mailing list at no c=
ost
to you by simply clicking here
<A HREF=3D"mailto:seok21@libero.it?Subject=3DRemove Please 101">Remove Ple=
ase</A>.
You will be promptly removed. Please note that interfering with this feder=
ally
approved method of removal will deny others the opportunity to be
removed.</FONT> </TD>
</TR>
</TABLE>
</DIV>
</HTML>
<p><p><p><p><p><p><p><p><p><p>
<!-- saved from url=3D(0022)http://internet.e-mail --><p> <p><HTML><p><p><=
p><p><DIV ALIGN=3D"center"><p><p><p><p><p><p><p><p><p>
</BODY>
</HTML>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message
From owner-freebsd-fs Wed Dec 6 18:32:44 2000
From owner-freebsd-fs@FreeBSD.ORG Wed Dec 6 18:32:43 2000
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from orvieto.eecs.harvard.edu (orvieto.eecs.harvard.edu [140.247.60.201])
by hub.freebsd.org (Postfix) with ESMTP id 6DDB637B400
for <freebsd-fs@freebsd.org>; Wed, 6 Dec 2000 18:32:42 -0800 (PST)
Received: from localhost (stein@localhost)
by orvieto.eecs.harvard.edu (8.9.3/8.9.3) with ESMTP id VAA07527
for <freebsd-fs@freebsd.org>; Wed, 6 Dec 2000 21:32:11 -0500 (EST)
(envelope-from stein@eecs.harvard.edu)
X-Authentication-Warning: orvieto.eecs.harvard.edu: stein owned process doing -bs
Date: Wed, 6 Dec 2000 21:32:11 -0500 (EST)
From: Christopher Stein <stein@eecs.harvard.edu>
To: freebsd-fs@freebsd.org
Subject: f_asyncwrites
Message-ID: <Pine.BSF.4.21.0012062129550.6699-100000@orvieto.eecs.harvard.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-fs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Can someone please tell me where the f_asyncwrites and f_syncwrites
fields of the mount structure's statfs structure are incremented.
I am having a devil of a time finding it. Grep is not turning anything
up.
thanks
-Chris
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message
From owner-freebsd-fs Wed Dec 6 21:18: 2 2000
From owner-freebsd-fs@FreeBSD.ORG Wed Dec 6 21:18:01 2000
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from hurlame.pdl.cs.cmu.edu (HURLAME.PDL.CS.CMU.EDU [128.2.189.78])
by hub.freebsd.org (Postfix) with ESMTP id 0575E37B400
for <freebsd-fs@freebsd.org>; Wed, 6 Dec 2000 21:17:59 -0800 (PST)
Received: (from magus@localhost)
by hurlame.pdl.cs.cmu.edu (8.11.1/8.11.1) id eB75HWl01783;
Thu, 7 Dec 2000 00:17:32 -0500 (EST)
(envelope-from magus)
Sender: magus@hurlame.pdl.cs.cmu.edu
To: Christopher Stein <stein@eecs.harvard.edu>
Cc: freebsd-fs@freebsd.org
Subject: Re: f_asyncwrites
References: <Pine.BSF.4.21.0012062129550.6699-100000@orvieto.eecs.harvard.edu>
From: Nat Lanza <magus@cs.cmu.edu>
Date: 07 Dec 2000 00:17:32 -0500
In-Reply-To: Christopher Stein's message of "Wed, 6 Dec 2000 21:32:11 -0500 (EST)"
Message-ID: <uocu28gstcj.fsf@hurlame.pdl.cs.cmu.edu>
Lines: 27
User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Channel Islands)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-fs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Christopher Stein <stein@eecs.harvard.edu> writes:
> Can someone please tell me where the f_asyncwrites and f_syncwrites
> fields of the mount structure's statfs structure are incremented.
The only thing I can see that touches it is spec_strategy(), in
miscfs/specfs/spec_vnops():
RELENG_4:
http://lxr.pdl.cs.cmu.edu/freebsd/source/miscfs/specfs/spec_vnops.c#L399
CURRENT:
http://lxr.pdl.cs.cmu.edu/freebsd/source/miscfs/specfs/spec_vnops.c?v=CURRENT#L397
> I am having a devil of a time finding it. Grep is not turning anything
> up.
I find that LXR works a lot better; it has identifier
cross-referencing, as well as glimpse-based fulltext search.
--nat
--
nat lanza --------------------- research programmer, parallel data lab, cmu scs
magus@cs.cmu.edu -------------------------------- http://www.cs.cmu.edu/~magus/
there are no whole truths; all truths are half-truths -- alfred north whitehead
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message
From owner-freebsd-fs Thu Dec 7 10:23:56 2000
From owner-freebsd-fs@FreeBSD.ORG Thu Dec 7 10:23:55 2000
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18])
by hub.freebsd.org (Postfix) with ESMTP id 2203337B401
for <freebsd-fs@FreeBSD.ORG>; Thu, 7 Dec 2000 10:23:55 -0800 (PST)
Received: from onyx (onyx.cs.binghamton.edu [128.226.140.171])
by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id NAA24834;
Thu, 7 Dec 2000 13:23:53 -0500 (EST)
Date: Thu, 7 Dec 2000 13:22:11 -0500 (EST)
From: Zhiui Zhang <zzhang@cs.binghamton.edu>
X-Sender: zzhang@onyx
To: Christopher Stein <stein@eecs.harvard.edu>
Cc: freebsd-fs@FreeBSD.ORG
Subject: Re: f_asyncwrites
In-Reply-To: <Pine.BSF.4.21.0012062129550.6699-100000@orvieto.eecs.harvard.edu>
Message-ID: <Pine.SOL.4.21.0012071321230.21496-100000@onyx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-fs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
On Wed, 6 Dec 2000, Christopher Stein wrote:
>
> Can someone please tell me where the f_asyncwrites and f_syncwrites
> fields of the mount structure's statfs structure are incremented.
>
> I am having a devil of a time finding it. Grep is not turning anything
> up.
I would try something like:
find /usr/src "*.c" -exec grep "f_asyncwrites" /dev/null {} \; | more
-Zhihui
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message
From owner-freebsd-fs Thu Dec 7 10:34:48 2000
From owner-freebsd-fs@FreeBSD.ORG Thu Dec 7 10:34:44 2000
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 870)
id 9741D37B400; Thu, 7 Dec 2000 10:34:44 -0800 (PST)
Date: Thu, 7 Dec 2000 10:34:44 -0800
From: Christoph Herrmann <chm@freebsd.org>
To: freebsd-current@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG
Subject: growfs(8) for FreeBSD
Message-ID: <20001207103444.B25381@freebsd.org>
Reply-To: growfs@tomsoft.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Sender: owner-freebsd-fs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Hi,
Due to vinum it is no problem to add disks and grow your volumes but up to
now you couldn't easily make use of that new space for a file system, except
using sequence of ufsdump/newfs/ufsrestore or something similar.
Thomas (tomsoft@freebsd.org) and me (chm@freebsd.org) have written a growfs(8)
for FreeBSD. Currently we can only grow unmounted file systems (in a clean
state) without any active snapshots inside. It is foreseen to enhance growfs to
grow mounted file systems as well, and handle active snapshots correctly.
This requires some infrastructure which is then only available in FreeBSD-5,
whilst the current design runs also happily on FreeBSD-4 and FreeBSD-3
(tested) and possibly even on FreeBSD-2 (untested).
To help us gathering the needed data for fixing bugs in growfs we additionally
wrote ffsinfo(8), a (very) extended version of dumpfs.
We've sent a couple of snapshots of our code to Kirk McKusick and to Greg
Lehey. Greg also volunteered :-) for reviewing the code. We also maintain
some sort of (for some contractual reasons unilaterally) contact with Don
Coleman who is doing the same thing for BSD/OS.
--
Ciao
Christoph &:-)
M$: Where do you want to go today?
Linux: Where do you want to go tomorrow?
FreeBSD: Are you guys comming, or what?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message
From owner-freebsd-fs Thu Dec 7 12:43:21 2000
From owner-freebsd-fs@FreeBSD.ORG Thu Dec 7 12:43:17 2000
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
by hub.freebsd.org (Postfix) with ESMTP
id 4968737B400; Thu, 7 Dec 2000 12:43:16 -0800 (PST)
Received: (from sos@localhost)
by freebsd.dk (8.9.3/8.9.1) id VAA68959;
Thu, 7 Dec 2000 21:45:40 +0100 (CET)
(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <200012072045.VAA68959@freebsd.dk>
Subject: Re: growfs(8) for FreeBSD
In-Reply-To: <20001207103444.B25381@freebsd.org> from Christoph Herrmann at "Dec 7, 2000 10:34:44 am"
To: growfs@tomsoft.com
Date: Thu, 7 Dec 2000 21:45:40 +0100 (CET)
Cc: freebsd-current@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-fs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
It seems Christoph Herrmann wrote:
Sounds very cool, but there is no URL :)
> Due to vinum it is no problem to add disks and grow your volumes but up to
> now you couldn't easily make use of that new space for a file system, except
> using sequence of ufsdump/newfs/ufsrestore or something similar.
>
> Thomas (tomsoft@freebsd.org) and me (chm@freebsd.org) have written a growfs(8)
> for FreeBSD. Currently we can only grow unmounted file systems (in a clean
> state) without any active snapshots inside. It is foreseen to enhance growfs to
> grow mounted file systems as well, and handle active snapshots correctly.
> This requires some infrastructure which is then only available in FreeBSD-5,
> whilst the current design runs also happily on FreeBSD-4 and FreeBSD-3
> (tested) and possibly even on FreeBSD-2 (untested).
>
> To help us gathering the needed data for fixing bugs in growfs we additionally
> wrote ffsinfo(8), a (very) extended version of dumpfs.
>
> We've sent a couple of snapshots of our code to Kirk McKusick and to Greg
> Lehey. Greg also volunteered :-) for reviewing the code. We also maintain
> some sort of (for some contractual reasons unilaterally) contact with Don
> Coleman who is doing the same thing for BSD/OS.
-Søren
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message
From owner-freebsd-fs Thu Dec 7 16:55:12 2000
From owner-freebsd-fs@FreeBSD.ORG Thu Dec 7 16:55:08 2000
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178])
by hub.freebsd.org (Postfix) with ESMTP
id BE50737B400; Thu, 7 Dec 2000 16:55:07 -0800 (PST)
Received: by peorth.iteration.net (Postfix, from userid 1001)
id 0B076573F5; Thu, 7 Dec 2000 18:55:30 -0600 (CST)
Date: Thu, 7 Dec 2000 18:55:29 -0600
From: "Michael C . Wu" <keichii@iteration.net>
To: growfs@tomsoft.com
Cc: freebsd-current@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG
Subject: Re: growfs(8) for FreeBSD
Message-ID: <20001207185529.A59719@peorth.iteration.net>
Reply-To: "Michael C . Wu" <keichii@peorth.iteration.net>
Mail-Followup-To: "Michael C . Wu" <keichii@iteration.net>,
growfs@tomsoft.com, freebsd-current@FreeBSD.ORG,
freebsd-fs@FreeBSD.ORG
References: <20001207103444.B25381@freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20001207103444.B25381@freebsd.org>; from chm@freebsd.org on Thu, Dec 07, 2000 at 10:34:44AM -0800
X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20
X-PGP-Key-ID: 0x8FA12E20
Sender: keichii@peorth.iteration.net
Sender: owner-freebsd-fs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
On Thu, Dec 07, 2000 at 10:34:44AM -0800, Christoph Herrmann scribbled:
| Due to vinum it is no problem to add disks and grow your volumes but up to
| now you couldn't easily make use of that new space for a file system, except
| using sequence of ufsdump/newfs/ufsrestore or something similar.
|
| Thomas (tomsoft@freebsd.org) and me (chm@freebsd.org) have written a growfs(8)
| for FreeBSD. Currently we can only grow unmounted file systems (in a clean
| state) without any active snapshots inside. It is foreseen to enhance growfs to
| grow mounted file systems as well, and handle active snapshots correctly.
| This requires some infrastructure which is then only available in FreeBSD-5,
| whilst the current design runs also happily on FreeBSD-4 and FreeBSD-3
| (tested) and possibly even on FreeBSD-2 (untested).
|
| To help us gathering the needed data for fixing bugs in growfs we additionally
| wrote ffsinfo(8), a (very) extended version of dumpfs.
Could you please put the code up somewhere that we can also look at?
--
+------------------------------------------------------------------+
| keichii@peorth.iteration.net | keichii@bsdconspiracy.net |
| http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. |
+------------------------------------------------------------------+
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message
From owner-freebsd-fs Fri Dec 8 2:19:19 2000
From owner-freebsd-fs@FreeBSD.ORG Fri Dec 8 02:19:17 2000
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
by hub.freebsd.org (Postfix) with ESMTP id 6617F37B400
for <freebsd-fs@FreeBSD.ORG>; Fri, 8 Dec 2000 02:19:16 -0800 (PST)
Received: (from des@localhost)
by flood.ping.uio.no (8.9.3/8.9.3) id LAA38014;
Fri, 8 Dec 2000 11:19:09 +0100 (CET)
(envelope-from des@ofug.org)
Sender: des@ofug.org
X-URL: http://www.ofug.org/~des/
X-Disclaimer: The views expressed in this message do not necessarily
coincide with those of any organisation or company with
which I am or have been affiliated.
To: Christopher Stein <stein@eecs.harvard.edu>
Cc: freebsd-fs@FreeBSD.ORG
Subject: Re: f_asyncwrites
References: <Pine.BSF.4.21.0012062129550.6699-100000@orvieto.eecs.harvard.edu>
From: Dag-Erling Smorgrav <des@ofug.org>
Date: 08 Dec 2000 11:19:08 +0100
In-Reply-To: Christopher Stein's message of "Wed, 6 Dec 2000 21:32:11 -0500 (EST)"
Message-ID: <xzpy9xr43mr.fsf@flood.ping.uio.no>
Lines: 42
User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-fs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Christopher Stein <stein@eecs.harvard.edu> writes:
> Can someone please tell me where the f_asyncwrites and f_syncwrites
> fields of the mount structure's statfs structure are incremented.
>
> I am having a devil of a time finding it. Grep is not turning anything
> up.
You may find the following useful in combination with
/usr/ports/textproc/glimpse:
#!/bin/sh
set -e
tag_current=""
tag_stable="-rRELENG_4"
[ -n "${branches}" ] || branches="current stable"
[ -n "${prefix}" ] || prefix="$(dirname $0)"
[ -n "${CVSROOT}" ] || CVSROOT="/home/ncvs"
export CVSROOT
# No user-serviceable parts beyond this point
for branch in ${branches} ; do
if [ ! -d ${prefix}/${branch}/src ] ; then
/usr/bin/install -d -m 755 ${prefix}/${branch}
cd ${prefix}/${branch}
eval "/usr/bin/cvs -d ${CVSROOT} checkout \${tag_$branch} src"
else
cd ${prefix}/${branch}/src
eval "/usr/bin/cvs -d ${CVSROOT} update \${tag_$branch}"
cd ${prefix}/${branch}
fi
find src -type f | egrep -v '/(.\#|CVS/)' |
/usr/local/bin/glimpseindex -B -F -o -H . -M 8
chmod a+r .glimpse*
cd -
done
DES
--
Dag-Erling Smorgrav - des@ofug.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message