From owner-freebsd-fs@FreeBSD.ORG Sun Feb 25 13:35:37 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8746916A400 for ; Sun, 25 Feb 2007 13:35:37 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 476C113C467 for ; Sun, 25 Feb 2007 13:35:33 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 771982087; Sun, 25 Feb 2007 14:35:29 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on tim.des.no Received: from dwp.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id 6A3A12085; Sun, 25 Feb 2007 14:35:29 +0100 (CET) Received: by dwp.des.no (Postfix, from userid 1001) id 39FE1B874; Sun, 25 Feb 2007 14:35:29 +0100 (CET) From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: "Steve Clement" References: <43302.62.229.116.183.1172042830.squirrel@webmail-lite.ion.lu> Date: Sun, 25 Feb 2007 14:35:28 +0100 In-Reply-To: <43302.62.229.116.183.1172042830.squirrel@webmail-lite.ion.lu> (Steve Clement's message of "Wed, 21 Feb 2007 08:27:10 +0100 (CET)") Message-ID: <867iu6bbrz.fsf@dwp.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: ZFS patches for FreeBSD. Makefile.inc1.rej X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Feb 2007 13:35:37 -0000 "Steve Clement" writes: > Using 6.2-RELEASE, the patches apply fine but Makefile.inc1 get's > rejected. The patches are for -CURRENT. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-fs@FreeBSD.ORG Tue Feb 27 09:41:07 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5233716A401 for ; Tue, 27 Feb 2007 09:41:07 +0000 (UTC) (envelope-from celso.vianna@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by mx1.freebsd.org (Postfix) with ESMTP id E079513C4A5 for ; Tue, 27 Feb 2007 09:41:04 +0000 (UTC) (envelope-from celso.vianna@gmail.com) Received: by ug-out-1314.google.com with SMTP id 71so964233ugh for ; Tue, 27 Feb 2007 01:41:03 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=jZcwnlqmxlw2QEbMKxwazUY5JEuIGfecaSo9vb2ZNpZCD4KassNhixbTPi8vKkQIOAI1BF9xGYlNz8v9wffoFDVTesm995hMIoY32KeWxuoNLR2Aa6E3XIZDY4dXhottDbzYws9htE2A4BjSOGxF2/GQnBu9RlJZeVMHtQnHoMk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=toCssiDW3sVVI8Er1vIsXjd5nUiL/bp8FY6pYzMr0lqmrvofpLzGklfYJtVdknEguAJYdJrIg4X56kkIoqujOO3iOMnjdWNI649haxN2MuznJsd7vPL81C4RVv+qbtPkRrvUX5wCQLZtpxuSKzo7bOUWRR1KGCzn3UrZEEau360= Received: by 10.78.106.3 with SMTP id e3mr552398huc.1172567617309; Tue, 27 Feb 2007 01:13:37 -0800 (PST) Received: by 10.78.160.9 with HTTP; Tue, 27 Feb 2007 01:13:37 -0800 (PST) Message-ID: <2b6bd2cc0702270113p6f704727n96da8e497e42b924@mail.gmail.com> Date: Tue, 27 Feb 2007 06:13:37 -0300 From: "Celso Viana" To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: automount (amd) and smbfs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2007 09:41:07 -0000 Hi all, Somebody knows if it is possible to use smfbs with amd (automount)? Thanks -- Celso Vianna BSD User: 51318 http://www.bsdcounter.org 63 8404-8559 Palmas/TO From owner-freebsd-fs@FreeBSD.ORG Wed Feb 28 05:44:25 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6436316E647 for ; Wed, 28 Feb 2007 05:44:24 +0000 (UTC) (envelope-from non_secure@yahoo.com) Received: from web51014.mail.yahoo.com (web51014.mail.yahoo.com [206.190.39.79]) by mx1.freebsd.org (Postfix) with SMTP id 181EF13C441 for ; Wed, 28 Feb 2007 05:44:23 +0000 (UTC) (envelope-from non_secure@yahoo.com) Received: (qmail 45809 invoked by uid 60001); 28 Feb 2007 05:17:42 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=44cX90bXOQ+u8ML6qbNCR72RbY4DW8pGYLUImt0Ol//msYBeeH142iMaoxtmuHeJ937dVx3JBgbrBWkA1UGKryjHgxFS9abEWL1MFR2E/ehjr0Q/ApXamOdZH5eLv0PkrHU71lrJKzSmnhu3NVIgMz23V26D6U70MZUUlWYV5hs=; X-YMail-OSG: IPkGbokVM1n7FLuYuHTpGCCz.BGxZxDuMy7tyPTTreWEUzCGO8kvh9VdC_ktEZSyJtT246TdlSjGlsiEZh6IvgyUDmHzJBBYm8ldUXV41YUMdvUbTzI9HVNAX8JCBZH_j5_vA.4luT0_bwMjHl.y17fM Received: from [75.72.230.91] by web51014.mail.yahoo.com via HTTP; Tue, 27 Feb 2007 21:17:42 PST Date: Tue, 27 Feb 2007 21:17:42 -0800 (PST) From: Jason Arnaute To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <660490.45660.qm@web51014.mail.yahoo.com> X-Mailman-Approved-At: Wed, 28 Feb 2007 12:48:49 +0000 Subject: Looking for a graceful way to disable BG fsck ? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Feb 2007 05:44:27 -0000 I do not particularly like to do a BG fsck - it takes forever and the system is near unusable while it goes ... and I don't mind just taking it down for a little while to get it over with. However, if I set the system: background_fsck="no" Then I have to wait for all mounts to fsck before the system will even come up on the network in a multi-user fashion. So what I am doing now is, if I have to reset a hung server, I quick race to log in, like an idiot, and hopefully log in and comment out the filesystems in fstab before 60 seconds expires and the bg fscks start. Because if I miss it, I'm screwed - you can't kill a BG fsck, and you can't reboot the system while a BG fsck is going on. So then you have to reset it again, which is scary because you've got a dirty filesystem, while being fsck'd, and then you dirty it up some more. So one plan is to just leave the non-root filesystems commented in /etc/fstab all the time, but that's not nice because if you ever need to legitimately (gracefully, on purpose) reboot, then they don't come up. Bleah. So my question is this: Is there any nice, elegant way to tell my system: "If everything is clean, then mount it all up and go. But if a non-root filesystem is not clean, just skip it altogether and boot up into multiuser mode and I will log in and fsck it manually. But under no circumstances will you BG fsck anything." Any way to do that ? ____________________________________________________________________________________ Need a quick answer? Get one in minutes from people who know. Ask your question on www.Answers.yahoo.com From owner-freebsd-fs@FreeBSD.ORG Wed Feb 28 13:08:57 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AEB0D16A402 for ; Wed, 28 Feb 2007 13:08:57 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: from web30312.mail.mud.yahoo.com (web30312.mail.mud.yahoo.com [209.191.69.74]) by mx1.freebsd.org (Postfix) with SMTP id 5E26413C471 for ; Wed, 28 Feb 2007 13:08:57 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: (qmail 18120 invoked by uid 60001); 28 Feb 2007 13:08:56 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=4kKCpdeZ3ohCd0XQO85WHxHn0kHc1pzv8TzPes30AbygFAU0h12DjOqGdGzZLTVgy1rVuxDKzv6QIXwmDHLlsykh0eAy7m9q0fA5VJNxiWVrtalhI3D4U9KrMlui88cx4YeuvT/H1PTKxSSRpy6tdnaRbVq7NyqARPzS3R3nn0c=; X-YMail-OSG: 7jarRZYVM1nv09CKdgKNOWKcdjV9TRBVFiCuW.BXpfC.xAjmQ_1nw7wzQmG_uxhRqaYT4SagMUsK67fYCgxAMKqatX28T8XaoO7eIdmzeAn3Ye7P3ydrEYyEwUjKi6_jwkHf59zJOL0O0ls- Received: from [213.54.173.42] by web30312.mail.mud.yahoo.com via HTTP; Wed, 28 Feb 2007 05:08:56 PST Date: Wed, 28 Feb 2007 05:08:56 -0800 (PST) From: "R. B. Riddick" To: Jason Arnaute , freebsd-fs@freebsd.org In-Reply-To: <660490.45660.qm@web51014.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <822542.17658.qm@web30312.mail.mud.yahoo.com> Cc: Subject: Re: Looking for a graceful way to disable BG fsck ? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Feb 2007 13:08:57 -0000 --- Jason Arnaute wrote: > Is there any nice, elegant way to tell my system: > > "If everything is clean, then mount it all up and go. > But if a non-root filesystem is not clean, just skip > it altogether and boot up into multiuser mode and I > will log in and fsck it manually. But under no > circumstances will you BG fsck anything." > > Any way to do that ? > You could change /etc/rc.d/fsck so that it will only fsck the root file system. Then you proceed with reboot... Then you look, if ur other file systems are mounted read-only and if yes, your box knows, that something was wrong with them...? WARNING: That idea needs testing... Furthermore your applications might complain, when they find their files on a read-only file system... -Arne ____________________________________________________________________________________ Have a burning question? Go to www.Answers.yahoo.com and get answers from real people who know. From owner-freebsd-fs@FreeBSD.ORG Wed Feb 28 13:13:43 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D72AD16A400 for ; Wed, 28 Feb 2007 13:13:43 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 7A2EA13C461 for ; Wed, 28 Feb 2007 13:13:43 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 27CAE47208; Wed, 28 Feb 2007 08:13:42 -0500 (EST) Date: Wed, 28 Feb 2007 13:13:42 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Jason Arnaute In-Reply-To: <660490.45660.qm@web51014.mail.yahoo.com> Message-ID: <20070228131227.K6955@fledge.watson.org> References: <660490.45660.qm@web51014.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@freebsd.org Subject: Re: Looking for a graceful way to disable BG fsck ? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Feb 2007 13:13:43 -0000 On Tue, 27 Feb 2007, Jason Arnaute wrote: > Because if I miss it, I'm screwed - you can't kill a BG fsck, and you can't > reboot the system while a BG fsck is going on. So then you have to reset it > again, which is scary because you've got a dirty filesystem, while being > fsck'd, and then you dirty it up some more. I'm not very informed on the rest of the issues here, but I can say that killing bgfsck is entirely possible. Send the fsck_ufs processes TERM signals, and then wait a bit and they will exit. I believe they finish whatever the current task they are working on is, then release the snapshot which can take a bit to free. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-fs@FreeBSD.ORG Wed Feb 28 13:21:33 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 079D216A402 for ; Wed, 28 Feb 2007 13:21:33 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.freebsd.org (Postfix) with ESMTP id D096713C442 for ; Wed, 28 Feb 2007 13:21:32 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id l1SDLWaM088726; Wed, 28 Feb 2007 07:21:32 -0600 (CST) (envelope-from anderson@freebsd.org) Message-ID: <45E581DF.4070706@freebsd.org> Date: Wed, 28 Feb 2007 07:21:35 -0600 From: Eric Anderson User-Agent: Thunderbird 1.5.0.9 (X11/20070204) MIME-Version: 1.0 To: "R. B. Riddick" References: <822542.17658.qm@web30312.mail.mud.yahoo.com> In-Reply-To: <822542.17658.qm@web30312.mail.mud.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/2679/Wed Feb 28 05:58:10 2007 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com Cc: freebsd-fs@freebsd.org, Jason Arnaute Subject: Re: Looking for a graceful way to disable BG fsck ? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Feb 2007 13:21:33 -0000 On 02/28/07 07:08, R. B. Riddick wrote: > --- Jason Arnaute wrote: >> Is there any nice, elegant way to tell my system: >> >> "If everything is clean, then mount it all up and go. >> But if a non-root filesystem is not clean, just skip >> it altogether and boot up into multiuser mode and I >> will log in and fsck it manually. But under no >> circumstances will you BG fsck anything." >> >> Any way to do that ? >> > You could change > /etc/rc.d/fsck > so that it will only fsck the root file system. > > Then you proceed with reboot... > > Then you look, if ur other file systems are mounted read-only and if yes, your > box knows, that something was wrong with them...? > > > WARNING: That idea needs testing... > > Furthermore your applications might complain, when they find their files on a > read-only file system... How about setting something like this: background_fsck_delay="864000" in /etc/rc.conf? That would make bg fsck wait 10 days before running. That will still mount the disks rw though, which is probably not what you really want. Eric From owner-freebsd-fs@FreeBSD.ORG Wed Feb 28 16:28:00 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0D5E916A402 for ; Wed, 28 Feb 2007 16:28:00 +0000 (UTC) (envelope-from ezk@agora.fsl.cs.sunysb.edu) Received: from filer.fsl.cs.sunysb.edu (filer.fsl.cs.sunysb.edu [130.245.126.2]) by mx1.freebsd.org (Postfix) with ESMTP id 94CFB13C481 for ; Wed, 28 Feb 2007 16:27:59 +0000 (UTC) (envelope-from ezk@agora.fsl.cs.sunysb.edu) Received: from agora.fsl.cs.sunysb.edu (agora.fsl.cs.sunysb.edu [130.245.126.12]) by filer.fsl.cs.sunysb.edu (8.12.11.20060308/8.13.1) with ESMTP id l1SGGZJB003635; Wed, 28 Feb 2007 11:16:35 -0500 Received: from agora.fsl.cs.sunysb.edu (localhost.localdomain [127.0.0.1]) by agora.fsl.cs.sunysb.edu (8.13.1/8.13.1) with ESMTP id l1SGGZxF026621; Wed, 28 Feb 2007 11:16:35 -0500 Received: (from ezk@localhost) by agora.fsl.cs.sunysb.edu (8.13.1/8.12.8/Submit) id l1SGGYlB026618; Wed, 28 Feb 2007 11:16:34 -0500 Date: Wed, 28 Feb 2007 11:16:34 -0500 Message-Id: <200702281616.l1SGGYlB026618@agora.fsl.cs.sunysb.edu> From: Erez Zadok To: "Celso Viana" In-reply-to: Your message of "Tue, 27 Feb 2007 06:13:37 -0300." <2b6bd2cc0702270113p6f704727n96da8e497e42b924@mail.gmail.com> X-MailKey: Erez_Zadok Cc: freebsd-fs@freebsd.org Subject: Re: automount (amd) and smbfs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Feb 2007 16:28:00 -0000 In message <2b6bd2cc0702270113p6f704727n96da8e497e42b924@mail.gmail.com>, "Celso Viana" writes: > Hi all, > > Somebody knows if it is possible to use smfbs with amd (automount)? Not directly, but using the type:=program type, you can invoke a user level program to mount anything. This section in the online manual shows how to set such a map entry with amd: http://www.am-utils.org/docs/am-utils/am-utils_10.html#SEC109 Erez. From owner-freebsd-fs@FreeBSD.ORG Wed Feb 28 18:32:23 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A2BB616A400 for ; Wed, 28 Feb 2007 18:32:23 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.freebsd.org (Postfix) with ESMTP id 7775713C4A5 for ; Wed, 28 Feb 2007 18:32:23 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id l1SIWMFT045343; Wed, 28 Feb 2007 12:32:22 -0600 (CST) (envelope-from anderson@freebsd.org) Message-ID: <45E5CABA.8070105@freebsd.org> Date: Wed, 28 Feb 2007 12:32:26 -0600 From: Eric Anderson User-Agent: Thunderbird 1.5.0.9 (X11/20070204) MIME-Version: 1.0 To: Jason Arnaute References: <629647.7934.qm@web51004.mail.yahoo.com> In-Reply-To: <629647.7934.qm@web51004.mail.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/2679/Wed Feb 28 05:58:10 2007 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com Cc: freebsd-fs@freebsd.org Subject: Re: Looking for a graceful way to disable BG fsck ? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Feb 2007 18:32:23 -0000 On 02/28/07 10:18, Jason Arnaute wrote: > --- Eric Anderson wrote: > > >> How about setting something like this: >> background_fsck_delay="864000" >> >> in /etc/rc.conf? That would make bg fsck wait 10 >> days before running. >> That will still mount the disks rw though, which is >> probably not what >> you really want. > > > Thanks - this may be the most useful way to do this. > > But you're right - it's not exactly what I want ... > provided that the critical filesystems are already > clean (all I have are /, /var, and (bulk_data)) I wish > it would just come up and say: > > "if they're clean, mount them and be happy. If > they're not, just _don't mount them_. Just don't do > anything. You've got your / and /var, so just be > happy and wait for someone to manually bring up > (bulk_data)" > > The reason this would work is that / and /var _always_ > get foreground fsck'd before the system can go > multi-user anyway ... so they are always safe ... You could work up a patch to the rc* stuff (plus maybe a few other tools) that would allow a new FSTAB_** define that means just that. Eric From owner-freebsd-fs@FreeBSD.ORG Wed Feb 28 16:18:22 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C0F7016A401 for ; Wed, 28 Feb 2007 16:18:22 +0000 (UTC) (envelope-from non_secure@yahoo.com) Received: from web51004.mail.yahoo.com (web51004.mail.yahoo.com [206.190.38.135]) by mx1.freebsd.org (Postfix) with SMTP id 5B32A13C461 for ; Wed, 28 Feb 2007 16:18:22 +0000 (UTC) (envelope-from non_secure@yahoo.com) Received: (qmail 8913 invoked by uid 60001); 28 Feb 2007 16:18:21 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=zhOATgDCjc77hllMU/v4NsGng7WnJxd9gz0kv/A68p+RLseYoFeV2OLR7s5Jz3O+2BuyUADnNV8HQeoq8Q4FZ0bFLr946NZjcsce3o4hWQSdNWbVd6lnXqd1TwadL9jUc3+vjTJrO6PFjsaLPVKwKWc1SF1dlnON7Cw007Aj5k8=; X-YMail-OSG: UbTAM70VM1lPylsl7YzkSq_ehNO0qOHFPmB3vD7FUbiEEvVDVKsBOek7lHY0LjIgZWMgGAGkfwqQnAzj5psaa9gx2qX0aJ2DLfsqUaklSruJOPE7mf61vXRm4Dzjq89NVLT5D0S6mVg- Received: from [75.72.230.91] by web51004.mail.yahoo.com via HTTP; Wed, 28 Feb 2007 08:18:21 PST Date: Wed, 28 Feb 2007 08:18:21 -0800 (PST) From: Jason Arnaute To: Eric Anderson , "R. B. Riddick" In-Reply-To: <45E581DF.4070706@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <629647.7934.qm@web51004.mail.yahoo.com> X-Mailman-Approved-At: Wed, 28 Feb 2007 22:13:28 +0000 Cc: freebsd-fs@freebsd.org, Jason Arnaute Subject: Re: Looking for a graceful way to disable BG fsck ? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Feb 2007 16:18:22 -0000 --- Eric Anderson wrote: > > How about setting something like this: > background_fsck_delay="864000" > > in /etc/rc.conf? That would make bg fsck wait 10 > days before running. > That will still mount the disks rw though, which is > probably not what > you really want. Thanks - this may be the most useful way to do this. But you're right - it's not exactly what I want ... provided that the critical filesystems are already clean (all I have are /, /var, and (bulk_data)) I wish it would just come up and say: "if they're clean, mount them and be happy. If they're not, just _don't mount them_. Just don't do anything. You've got your / and /var, so just be happy and wait for someone to manually bring up (bulk_data)" The reason this would work is that / and /var _always_ get foreground fsck'd before the system can go multi-user anyway ... so they are always safe ... ____________________________________________________________________________________ Want to start your own business? Learn how on Yahoo! Small Business. http://smallbusiness.yahoo.com/r-index From owner-freebsd-fs@FreeBSD.ORG Thu Mar 1 14:08:15 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6681716A400; Thu, 1 Mar 2007 14:08:15 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from natial.ongs.co.jp (natial.ongs.co.jp [202.216.232.58]) by mx1.freebsd.org (Postfix) with ESMTP id E9D6B13C441; Thu, 1 Mar 2007 14:08:12 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from [192.168.1.101] (dullmdaler.ongs.co.jp [202.216.232.62]) by natial.ongs.co.jp (Postfix) with ESMTP id 4C403244C19; Thu, 1 Mar 2007 22:42:20 +0900 (JST) Message-ID: <45E6D83C.9030206@freebsd.org> Date: Thu, 01 Mar 2007 22:42:20 +0900 From: Daichi GOTO User-Agent: Thunderbird 1.5.0.9 (X11/20070119) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, freebsd-fs@freebsd.org, rodrigc@crodrigues.org Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Cc: daichi@freebsd.org, kris@obsecurity.org Subject: [ANN] unionfs patchset-18 release, improvements are going step by step X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Mar 2007 14:08:15 -0000 Hi Guys! It is my pleasure and honor to announce the availability of the unionfs patchset-18. p18 is first patchset after its merged of FreeBSD. Our improvements works of unionfs are going step by step. Patchset-18: For 7-current http://people.freebsd.org/~daichi/unionfs/unionfs-p18.diff For 6-stable http://people.freebsd.org/~daichi/unionfs/unionfs6-p18.diff Changes in unionfs-p18.diff - Improve access permission check treatments. - Change it free unneeded memory ASAP. - Added treatments to prevent readdir infinity loop useing with Linux binary compatibility feature. The documents of those unionfs patches: http://people.freebsd.org/~daichi/unionfs/ (English) http://people.freebsd.org/~daichi/unionfs/index-ja.html (Japanese) For unionfs lovers including FreeSBIE developers, ports cluster managers, heavy memory-fs users, and folks use unionfs, could you try p18 please? If p18 works well, please merge it to -current/-stable, rodrigc :) Thanks -- Daichi GOTO, http://people.freebsd.org/~daichi From owner-freebsd-fs@FreeBSD.ORG Thu Mar 1 14:14:14 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A87D316A402; Thu, 1 Mar 2007 14:14:14 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from natial.ongs.co.jp (natial.ongs.co.jp [202.216.232.58]) by mx1.freebsd.org (Postfix) with ESMTP id 3AE7613C471; Thu, 1 Mar 2007 14:14:14 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from [192.168.1.101] (dullmdaler.ongs.co.jp [202.216.232.62]) by natial.ongs.co.jp (Postfix) with ESMTP id 8B236244C31; Thu, 1 Mar 2007 23:14:11 +0900 (JST) Message-ID: <45E6DFB3.5070805@freebsd.org> Date: Thu, 01 Mar 2007 23:14:11 +0900 From: Daichi GOTO User-Agent: Thunderbird 1.5.0.9 (X11/20070119) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, freebsd-fs@freebsd.org, rodrigc@crodrigues.org Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Cc: daichi@freebsd.org, kris@obsecurity.org Subject: [Request for Test] unionfs procfs/vfs_cache support tester we need X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Mar 2007 14:14:14 -0000 Hi Guys! We have patch of unionfs that supports procfs/vfs_cache. With this patch, you can use application that use procfs on unionfs. unionfs patch for procfs/vfs_cache support: document http://people.freebsd.org/~daichi/unionfs/request-for-test.html For 7-current http://people.freebsd.org/~daichi/unionfs/unionfs-procfs-sup.diff For 6-stable http://people.freebsd.org/~daichi/unionfs/unionfs6-procfs-sup.diff The unionfs lovers, would you do test that patch please? If you have no trouble, it'll be merged to common unionfs patch :) Thanks -- Daichi GOTO, http://people.freebsd.org/~daichi From owner-freebsd-fs@FreeBSD.ORG Thu Mar 1 14:21:18 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0EBDA16A401; Thu, 1 Mar 2007 14:21:18 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from natial.ongs.co.jp (natial.ongs.co.jp [202.216.232.58]) by mx1.freebsd.org (Postfix) with ESMTP id 8E6B413C428; Thu, 1 Mar 2007 14:21:17 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from [192.168.1.101] (dullmdaler.ongs.co.jp [202.216.232.62]) by natial.ongs.co.jp (Postfix) with ESMTP id 905EB244C19; Thu, 1 Mar 2007 23:21:15 +0900 (JST) Message-ID: <45E6E15B.5000104@freebsd.org> Date: Thu, 01 Mar 2007 23:21:15 +0900 From: Daichi GOTO User-Agent: Thunderbird 1.5.0.9 (X11/20070119) MIME-Version: 1.0 To: Ed Schouten References: <45E6D83C.9030206@freebsd.org> <20070301141357.GA41996@hoeg.nl> In-Reply-To: <20070301141357.GA41996@hoeg.nl> Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Cc: FreeBSD Hackers , freebsd-fs@freebsd.org, FreeBSD Current , kris@obsecurity.org Subject: Re: [ANN] unionfs patchset-18 release, improvements are going step by step X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Mar 2007 14:21:18 -0000 Ed Schouten wrote: > * Daichi GOTO wrote: >> It is my pleasure and honor to announce the availability of the >> unionfs patchset-18. p18 is first patchset after its merged of >> FreeBSD. Our improvements works of unionfs are going step by step. > > Are there still plans to add my whiteout policy patch? > > http://g-rave.nl/junk/freebsd-unionfs-prevent-whiteout.diff > > Yours, Yeah, yeah. Sorry of my slow response. We are considering your patch always. We suppose we'll add your patch into our patch in future patchset. The plan: 1. include your patch into our patch 2. release it for unionfs lovers 3. after evaluation of guys 4. we'll give it our justice (IMO, it's good for merge) I,m sorry again of my slow response. It's my sorry. -- Daichi GOTO, http://people.freebsd.org/~daichi From owner-freebsd-fs@FreeBSD.ORG Thu Mar 1 14:31:37 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 94DDC16A400 for ; Thu, 1 Mar 2007 14:31:37 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (palm.hoeg.nl [83.98.131.212]) by mx1.freebsd.org (Postfix) with ESMTP id 60E9613C467 for ; Thu, 1 Mar 2007 14:31:37 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id A95EA1CC8E; Thu, 1 Mar 2007 15:13:57 +0100 (CET) Date: Thu, 1 Mar 2007 15:13:57 +0100 From: Ed Schouten To: Daichi GOTO Message-ID: <20070301141357.GA41996@hoeg.nl> References: <45E6D83C.9030206@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HcAYCG3uE/tztfnV" Content-Disposition: inline In-Reply-To: <45E6D83C.9030206@freebsd.org> User-Agent: Mutt/1.5.14 (2007-02-12) Cc: FreeBSD Hackers , freebsd-fs@freebsd.org, FreeBSD Current , kris@obsecurity.org Subject: Re: [ANN] unionfs patchset-18 release, improvements are going step by step X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Mar 2007 14:31:37 -0000 --HcAYCG3uE/tztfnV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Daichi GOTO wrote: > It is my pleasure and honor to announce the availability of the > unionfs patchset-18. p18 is first patchset after its merged of > FreeBSD. Our improvements works of unionfs are going step by step. Are there still plans to add my whiteout policy patch? http://g-rave.nl/junk/freebsd-unionfs-prevent-whiteout.diff Yours, --=20 Ed Schouten WWW: http://g-rave.nl/ --HcAYCG3uE/tztfnV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFF5t+l52SDGA2eCwURAhIjAJkBg4PjCZTemfCXoj8lrTxmvkxGiQCcCs6z 13lwZvK38h+WUUo9GHcFMPs= =aBAR -----END PGP SIGNATURE----- --HcAYCG3uE/tztfnV-- From owner-freebsd-fs@FreeBSD.ORG Fri Mar 2 14:45:43 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4451816A408 for ; Fri, 2 Mar 2007 14:45:43 +0000 (UTC) (envelope-from mwest@cs.uct.ac.za) Received: from mx-out.cs.uct.ac.za (mx-out.cs.uct.ac.za [137.158.96.39]) by mx1.freebsd.org (Postfix) with ESMTP id DDF3E13C4AC for ; Fri, 2 Mar 2007 14:45:42 +0000 (UTC) (envelope-from mwest@cs.uct.ac.za) Received: from mwest by casper2.cs.uct.ac.za with local (Exim 4.42 (FreeBSD)) id 1HN8Ze-000KbB-D4; Fri, 02 Mar 2007 16:17:30 +0200 Date: Fri, 2 Mar 2007 16:17:30 +0200 From: Matthew West To: freebsd-fs@freebsd.org Message-ID: <20070302141730.GA78630@cs.uct.ac.za> References: <45E581DF.4070706@freebsd.org> <629647.7934.qm@web51004.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <629647.7934.qm@web51004.mail.yahoo.com> User-Agent: Mutt/1.4.2.1i Cc: Jason Arnaute Subject: Re: Looking for a graceful way to disable BG fsck ? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2007 14:45:43 -0000 On Wed, Feb 28, 2007 at 08:18:21AM -0800, Jason Arnaute wrote: > But you're right - it's not exactly what I want ... > provided that the critical filesystems are already > clean (all I have are /, /var, and (bulk_data)) I wish > it would just come up and say: > > "if they're clean, mount them and be happy. If > they're not, just _don't mount them_. Just don't do > anything. You've got your / and /var, so just be > happy and wait for someone to manually bring up > (bulk_data)" A cheap-and-nasty way would be to add the "noauto" option for your "(bulk_data)" in /etc/fstab, and then do something like put "mount (bulk_data)" into /etc/rc.local. If the "(bulk_data)" FS is clean, it'll get mounted at boot time. If it's dirty, mount will output an error to console, but the system will be unaffected otherwise. You could even have it fallback to mounting "(bulk_data)" as read-only if you required such a thing. -- mwest@cs.uct.ac.za From owner-freebsd-fs@FreeBSD.ORG Fri Mar 2 20:00:48 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 99B0816A402 for ; Fri, 2 Mar 2007 20:00:48 +0000 (UTC) (envelope-from adamlsd@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.226]) by mx1.freebsd.org (Postfix) with ESMTP id 5792113C4A3 for ; Fri, 2 Mar 2007 20:00:48 +0000 (UTC) (envelope-from adamlsd@gmail.com) Received: by wx-out-0506.google.com with SMTP id s18so805898wxc for ; Fri, 02 Mar 2007 12:00:48 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer:sender; b=flou1yJ/cZyxwJZtIpGv5xKMg/2HcPoqM3xKOkR2qpWVm9Pg0q02EfNXApGEXGRSTxL87e+Loag+l3x5+z1F6h73dZg5um/ZEF9UnIxY7kdoN1PWfwk9nNXlKucv7gX5RpdkLLYDZ9hXEDgzTioY1LuXY1rfmMdNmpuE/0bXoF0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer:sender; b=tvwRypNO/dcy9CjD5+d4JWpaNKIaclwzoGk+hJvm0IcTjpiCe32XwL8Aj4m8DQKr1TqMNq034TTBtfkdIWlvh2gFbGg6B5HSWrIxrmAF6msqySjIzrajNay0IVlTSVlkYCPlnUz6NQbxLUzTfse2q7wIKWNBIR3ua4jARpwE1Sg= Received: by 10.90.71.12 with SMTP id t12mr3226364aga.1172863971322; Fri, 02 Mar 2007 11:32:51 -0800 (PST) Received: from ?129.49.5.118? ( [129.49.5.118]) by mx.google.com with ESMTP id 34sm4663016wra.2007.03.02.11.32.50; Fri, 02 Mar 2007 11:32:50 -0800 (PST) In-Reply-To: <45E581DF.4070706@freebsd.org> References: <822542.17658.qm@web30312.mail.mud.yahoo.com> <45E581DF.4070706@freebsd.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <206E31A0-C35D-462E-9C31-65ECFCDFC16B@FreeBSD.org> Content-Transfer-Encoding: 7bit From: Adam Martin Date: Fri, 2 Mar 2007 14:32:48 -0500 To: freebsd-fs@freebsd.org X-Mailer: Apple Mail (2.752.2) Sender: Adam Martin Cc: ADAM David Alan Martin Subject: Re: Looking for a graceful way to disable BG fsck ? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2007 20:00:48 -0000 All, On Feb 28, 2007, at 8:21 AM, Eric Anderson wrote: > On 02/28/07 07:08, R. B. Riddick wrote: >> --- Jason Arnaute wrote: >>> Is there any nice, elegant way to tell my system: >>> >>> "If everything is clean, then mount it all up and go. But if a >>> non-root filesystem is not clean, just skip >>> it altogether and boot up into multiuser mode and I >>> will log in and fsck it manually. But under no >>> circumstances will you BG fsck anything." >>> >>> Any way to do that ? > > How about setting something like this: > background_fsck_delay="864000" > > in /etc/rc.conf? That would make bg fsck wait 10 days before > running. That will still mount the disks rw though, which is > probably not what you really want. I do a large amount of kernel modifications (I'm developing a new filesystem). Resultingly, every few hours, I'm bound to panic the kernel, from some stupid mistake I'll make. I set my background_fsck_delay to an appropriately large value, myself. It's worked well for me, on the test box that I have. (In my case, about 6000 seconds has been the magic value. If the system's up for more than 2 hours, it's not likely to go down any time soon -- I've likely wrapped up for the day. So the discs can now start checking.) Incidentally, the background_fsck_delay is just used as an argument to sleep(1). You could set it to a value on the order of months or years, and just kill the sleep launched by /etc/rc.d/bgfsck, when you want to force the discs to fsck. (Otherwise the discs will not fsck.) While waiting for this bgfsck-sleep, it seems safe, in my experience, to force a bgfsck on any mounted filesystem. (/sbin/fsck isn't launched, it's waiting on sleep(1) to finish, so I'd wager it's totally safe. I've never had problems with double fscking a filesystem. But I never had 2 concurrent bgfscks run on a filesystem...) As I understand it, it can be wise to have the bgfsck run at some point, however. About a year ago, I had a failing disc controller, which kept panicking the kernel, and I got munged data on the drive (particularly in the ufs data structures). Even after replacing the controller, the resultant fs-corruption kept panicking the kernel in the vfs. When in single-user, I forced a fsck on the filesystems, in foreground, and that solved everything. Luckily I didn't lose any important data (most of the time the vfs would panic the kernel on file creation.) So I would suggest that you not glaze over the need to fsck. (You may want to have bgfsck use atq, to schedule some form of fsck at a specific time when you expect low system usage.) That's just my 0.02USD. -- ADAM David Alan Martin From owner-freebsd-fs@FreeBSD.ORG Fri Mar 2 20:24:09 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9C52516A400 for ; Fri, 2 Mar 2007 20:24:09 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (grnl-static-02-0046.dsl.iowatelecom.net [69.66.56.110]) by mx1.freebsd.org (Postfix) with ESMTP id ECB5513C4AC for ; Fri, 2 Mar 2007 20:24:08 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.13.8/8.13.8) with ESMTP id l22KO6Ga082276; Fri, 2 Mar 2007 14:24:06 -0600 (CST) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.13.8/8.13.8/Submit) id l22KO5XG082274; Fri, 2 Mar 2007 14:24:05 -0600 (CST) (envelope-from brooks) Date: Fri, 2 Mar 2007 14:24:05 -0600 From: Brooks Davis To: Adam Martin Message-ID: <20070302202405.GA81873@lor.one-eyed-alien.net> References: <822542.17658.qm@web30312.mail.mud.yahoo.com> <45E581DF.4070706@freebsd.org> <206E31A0-C35D-462E-9C31-65ECFCDFC16B@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EVF5PPMfhYS0aIcm" Content-Disposition: inline In-Reply-To: <206E31A0-C35D-462E-9C31-65ECFCDFC16B@FreeBSD.org> User-Agent: Mutt/1.5.11 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (lor.one-eyed-alien.net [127.0.0.1]); Fri, 02 Mar 2007 14:24:06 -0600 (CST) Cc: freebsd-fs@freebsd.org, ADAM David Alan Martin Subject: Re: Looking for a graceful way to disable BG fsck ? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2007 20:24:09 -0000 --EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 02, 2007 at 02:32:48PM -0500, Adam Martin wrote: > All, >=20 > On Feb 28, 2007, at 8:21 AM, Eric Anderson wrote: >=20 > >On 02/28/07 07:08, R. B. Riddick wrote: > >>--- Jason Arnaute wrote: > >>>Is there any nice, elegant way to tell my system: > >>> > >>>"If everything is clean, then mount it all up and go. But if a =20 > >>>non-root filesystem is not clean, just skip > >>>it altogether and boot up into multiuser mode and I > >>>will log in and fsck it manually. But under no > >>>circumstances will you BG fsck anything." > >>> > >>>Any way to do that ? > > > >How about setting something like this: > >background_fsck_delay=3D"864000" > > > >in /etc/rc.conf? That would make bg fsck wait 10 days before =20 > >running. That will still mount the disks rw though, which is =20 > >probably not what you really want. >=20 > I do a large amount of kernel modifications (I'm developing a new =20 > filesystem). Resultingly, every few hours, I'm bound to panic the =20 > kernel, from some stupid mistake I'll make. I set my =20 > background_fsck_delay to an appropriately large value, myself. It's =20 > worked well for me, on the test box that I have. (In my case, about =20 > 6000 seconds has been the magic value. If the system's up for more =20 > than 2 hours, it's not likely to go down any time soon -- I've likely =20 > wrapped up for the day. So the discs can now start checking.) >=20 > Incidentally, the background_fsck_delay is just used as an argument =20 > to sleep(1). You could set it to a value on the order of months or =20 > years, and just kill the sleep launched by /etc/rc.d/bgfsck, when you =20 > want to force the discs to fsck. (Otherwise the discs will not fsck.) >=20 > While waiting for this bgfsck-sleep, it seems safe, in my =20 > experience, to force a bgfsck on any mounted filesystem. (/sbin/fsck =20 > isn't launched, it's waiting on sleep(1) to finish, so I'd wager it's =20 > totally safe. I've never had problems with double fscking a =20 > filesystem. But I never had 2 concurrent bgfscks run on a =20 > filesystem...) >=20 > As I understand it, it can be wise to have the bgfsck run at some =20 > point, however. About a year ago, I had a failing disc controller, =20 > which kept panicking the kernel, and I got munged data on the drive =20 > (particularly in the ufs data structures). Even after replacing the =20 > controller, the resultant fs-corruption kept panicking the kernel in =20 > the vfs. When in single-user, I forced a fsck on the filesystems, in =20 > foreground, and that solved everything. Luckily I didn't lose any =20 > important data (most of the time the vfs would panic the kernel on =20 > file creation.) So I would suggest that you not glaze over the need =20 > to fsck. (You may want to have bgfsck use atq, to schedule some form =20 > of fsck at a specific time when you expect low system usage.) The following patch allows you to delay the bgfsck indefinitly and then run it later by running with bgfsck with forcestart. I've suppressed all output in the forcestart case to allow it to be run out of cron. It seems to be working for me. -- Brooks Index: etc/rc.d/bgfsck =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /usr/cvs/src/etc/rc.d/bgfsck,v retrieving revision 1.7 diff -u -p -r1.7 bgfsck --- etc/rc.d/bgfsck 22 Jul 2005 00:57:37 -0000 1.7 +++ etc/rc.d/bgfsck 12 Feb 2007 19:53:12 -0000 @@ -16,11 +16,23 @@ stop_cmd=3D":" =20 bgfsck_start () { + if [ -z "${rc_force}" ]; then + background_fsck_delay=3D${background_fsck_delay:=3D0} + else + background_fsck_delay=3D0 + fi + if [ ${background_fsck_delay} -lt 0 ]; then + echo "Background file system checks delayed indefinitly" + return 0 + fi + bgfsck_msg=3D'Starting background file system checks' - if [ ${background_fsck_delay:=3D0} -gt 0 ]; then + if [ "${background_fsck_delay}" -gt 0 ]; then bgfsck_msg=3D"${bgfsck_msg} in ${background_fsck_delay} seconds" fi - echo "${bgfsck_msg}." + if [ -z "${rc_force}" ]; then + echo "${bgfsck_msg}." + fi =20 (sleep ${background_fsck_delay}; nice -4 fsck -B -p) 2>&1 | \ logger -p daemon.notice -t fsck & Index: share/man/man5/rc.conf.5 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /usr/cvs/src/share/man/man5/rc.conf.5,v retrieving revision 1.314 diff -u -p -r1.314 rc.conf.5 --- share/man/man5/rc.conf.5 24 Jan 2007 09:22:56 -0000 1.314 +++ share/man/man5/rc.conf.5 2 Mar 2007 20:19:31 -0000 @@ -1359,6 +1359,15 @@ The amount of time in seconds to sleep b It defaults to sixty seconds to allow large applications such as the X server to start before disk I/O bandwidth is monopolized by .Xr fsck 8 . +If set to a negative number, the background file system check will be +delayed indefinitely to allow the administrator to run it at a more +convenient time. +For example it may be run from cron by adding a line like +.Pp +.Dl 0 4 * * * root /etc/rc.d/bgfsck forcestart +.Pp +to +.Pa /etc/crontab . .It Va netfs_types .Pq Vt str List of file system types that are network-based. --EVF5PPMfhYS0aIcm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFF6IfkXY6L6fI4GtQRAnfXAKCRtBzhjw/esWUnbbC5xw2B5Yq4OQCbBCmX BJ0W6hwCXv5JGw/M8zCC2OU= =ZMZG -----END PGP SIGNATURE----- --EVF5PPMfhYS0aIcm-- From owner-freebsd-fs@FreeBSD.ORG Sat Mar 3 09:22:07 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 83E2116A401 for ; Sat, 3 Mar 2007 09:22:07 +0000 (UTC) (envelope-from shilps4u.always@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.229]) by mx1.freebsd.org (Postfix) with ESMTP id 42EDA13C491 for ; Sat, 3 Mar 2007 09:22:07 +0000 (UTC) (envelope-from shilps4u.always@gmail.com) Received: by wx-out-0506.google.com with SMTP id s18so933748wxc for ; Sat, 03 Mar 2007 01:22:06 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=PzHlNbkkLVQpES54kbFPkjETBuPQtWep/jEgQnuhmhU3LJ4GG27iJNPwIT39EJbHvUj56U0Fre7hFW3zUY+CaWAxlOJglUuKczDGEq3GaqgOtJhq9jOuVyNXc3ydUp+uqrXaSpMQt5PIX5KTqGT04DLQ4bE7hWKl2nCb5GjRphE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=a/UBzphg731DsMAfYeuaS1AGDzNI2P0YlLziaQQuCBCqsHffa1xB8Aia9rVpy2WpHsudaJU0CZBBbZeq72HVU0lYR4Z2tEUG6rrdnLoUOZMFxYGnpva29Nk89KHz6mQU/7xtCegEhT33he65T2FNtZOwp9KffUCAwC5QO7DCg4A= Received: by 10.90.75.10 with SMTP id x10mr3622222aga.1172912142821; Sat, 03 Mar 2007 00:55:42 -0800 (PST) Received: by 10.90.94.8 with HTTP; Sat, 3 Mar 2007 00:55:42 -0800 (PST) Message-ID: <9b023eb20703030055n6a7299dctbb5c9d533f2c765@mail.gmail.com> Date: Sat, 3 Mar 2007 14:25:42 +0530 From: "shilpa kheria" To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: yfs implementation in freebsd 4.5 release X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2007 09:22:07 -0000 is there any way by which i can get access of the FreeBSD 4.5 release code for yFS,,,i wanted to have a look on the lightweight journaling implementation thr..