From owner-freebsd-fs@FreeBSD.ORG Sun Feb 20 00:47:35 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 798DF106566B for ; Sun, 20 Feb 2011 00:47:35 +0000 (UTC) (envelope-from piotr.kucharski@42.pl) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 1A28C8FC19 for ; Sun, 20 Feb 2011 00:47:34 +0000 (UTC) Received: by wwf26 with SMTP id 26so4863244wwf.31 for ; Sat, 19 Feb 2011 16:47:34 -0800 (PST) Received: by 10.216.71.209 with SMTP id r59mr917668wed.15.1298162854168; Sat, 19 Feb 2011 16:47:34 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.5.74 with HTTP; Sat, 19 Feb 2011 16:46:54 -0800 (PST) X-Originating-IP: [84.74.143.69] In-Reply-To: References: From: Piotr Kucharski Date: Sun, 20 Feb 2011 01:46:54 +0100 Message-ID: To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 Subject: Re: very slow zfs scrub 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, 20 Feb 2011 00:47:35 -0000 FWIW, it was the same on zpool v15, I upgraded in vain hope of improvement. scrub stats improved. :) From owner-freebsd-fs@FreeBSD.ORG Sun Feb 20 00:56:36 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E1F31065673 for ; Sun, 20 Feb 2011 00:56:36 +0000 (UTC) (envelope-from piotr.kucharski@42.pl) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 419AE8FC0A for ; Sun, 20 Feb 2011 00:56:35 +0000 (UTC) Received: by wwf26 with SMTP id 26so4866742wwf.31 for ; Sat, 19 Feb 2011 16:56:35 -0800 (PST) Received: by 10.216.185.199 with SMTP id u49mr2312943wem.45.1298161945149; Sat, 19 Feb 2011 16:32:25 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.5.74 with HTTP; Sat, 19 Feb 2011 16:31:45 -0800 (PST) X-Originating-IP: [84.74.143.69] From: Piotr Kucharski Date: Sun, 20 Feb 2011 01:31:45 +0100 Message-ID: To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 Subject: very slow zfs scrub 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, 20 Feb 2011 00:56:36 -0000 FreeBSD 8.2-PRERELEASE #18 r218734M with zfs28 patch applied, machine has 24G ram, 2 package(s) x 4 core(s) x 2 SMT threads (Xeon E5620 @ 2.40GHz) and is 99% idle. # date Sun Feb 20 01:17:05 CET 2011 # zpool status vol pool: vol state: ONLINE scan: scrub in progress since Fri Feb 18 05:24:55 2011 163G scanned out of 8.28T at 1.06M/s, (scan is slow, no estimated time) 0 repaired, 1.93% done config: NAME STATE READ WRITE CKSUM vol ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 ggate1.eli ONLINE 0 0 0 ggate3.eli ONLINE 0 0 0 ggate2.eli ONLINE 0 0 0 ggate4.eli ONLINE 0 0 0 ggate5.eli ONLINE 0 0 0 ggate6.eli ONLINE 0 0 0 ggate7.eli ONLINE 0 0 0 ggate8.eli ONLINE 0 0 0 ggate9.eli ONLINE 0 0 0 ggate10.eli ONLINE 0 0 0 ggate11.eli ONLINE 0 0 0 ggate12.eli ONLINE 0 0 0 logs mirror-1 ONLINE 0 0 0 da0p4 ONLINE 0 0 0 da1p4 ONLINE 0 0 0 ggateX.eli are (obviously) geli over ggate devices located in the same LAN, no special setup. Under normal circumstances performance is fine, at least 20MB/s transfers for files, no problem with multiple accesses etc. It's okay for me. zfs scrub, however, is completely different story a) it is very slow (as you can see above) b) it makes zfs very slow: # dd if=/vol/file of=/dev/null bs=64k [several ^T] load: 0.01 cmd: dd 98988 [zfs] 3.00r 0.00u 0.00s 0% 832k load: 0.01 cmd: dd 98988 [zio->io_cv)] 19.66r 0.00u 0.00s 0% 900k load: 0.01 cmd: dd 98988 [zio->io_cv)] 20.43r 0.00u 0.00s 0% 900k 34+0 records in 34+0 records out 2228224 bytes transferred in 15.816547 secs (140879 bytes/sec) 34+0 records in 34+0 records out 2228224 bytes transferred in 15.816555 secs (140879 bytes/sec) 34+0 records in 34+0 records out 2228224 bytes transferred in 15.816562 secs (140879 bytes/sec) ^C98+0 records in 98+0 records out 6422528 bytes transferred in 46.926860 secs (136863 bytes/sec) it looks like some of the ggate.eli's get hammered by scrub and performance goes down the drain: # for i in {1..12}; do echo -n "ggate$i.eli "; dd if=/dev/ggate$i.eli of=/dev/null bs=64k skip=$((RANDOM*100)) count=100 2>&1 | grep transferred; done ggate1.eli 6553600 bytes transferred in 0.323291 secs (20271516 bytes/sec) ggate2.eli 6553600 bytes transferred in 0.278870 secs (23500567 bytes/sec) ggate3.eli 6553600 bytes transferred in 0.541883 secs (12094124 bytes/sec) ggate4.eli 6553600 bytes transferred in 30.822238 secs (212626 bytes/sec) ggate5.eli 6553600 bytes transferred in 0.927459 secs (7066188 bytes/sec) ggate6.eli 6553600 bytes transferred in 0.346056 secs (18937976 bytes/sec) ggate7.eli 6553600 bytes transferred in 0.279477 secs (23449525 bytes/sec) ggate8.eli 6553600 bytes transferred in 29.028139 secs (225767 bytes/sec) ggate9.eli 6553600 bytes transferred in 0.422382 secs (15515817 bytes/sec) ggate10.eli 6553600 bytes transferred in 0.278718 secs (23513372 bytes/sec) ggate11.eli 6553600 bytes transferred in 0.308250 secs (21260652 bytes/sec) ggate12.eli 6553600 bytes transferred in 29.901194 secs (219175 bytes/sec) (geli eats half of the raw speeds, but that I expected) The second I stop the scrub, everything goes back to normal. I decided to ride it out for a while (despite it making this pool basically unusable), as I've heard scrub speed is abysmal in the beginning and significantly speeds up. But that still didn't happen. Anyone seen similar behaviour? Any advice (other than bringing the disks locally) to fix this? From owner-freebsd-fs@FreeBSD.ORG Sun Feb 20 07:26:29 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1F1D4106564A for ; Sun, 20 Feb 2011 07:26:29 +0000 (UTC) (envelope-from s.dave.jones@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id DCACF8FC17 for ; Sun, 20 Feb 2011 07:26:28 +0000 (UTC) Received: by iwn39 with SMTP id 39so5138003iwn.13 for ; Sat, 19 Feb 2011 23:26:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=ItlBALxB1qDl4f2yLq8v+gQZW45vfClM3tV3ZiUTz8E=; b=U2sAegKAlU43xhsoYbS0jRYciWuUOmMs3fTjn30VtWS40OklLI65dupl2RCS1G6AqX zgcFjqMILtiP4I4rL6v4mdEP5qbxZPt4E9wm8qizY2lQd3xrb9w0XMwkdwrePv4rPoZP b4Z2njVHazbVOlKvxAI8BGfTz/D0OA/O4euC4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=B4neUXBIjLwARk7RjtucfaACYV0yYyZBf6FPKoew1tInepUzdd4uLzvBshS4V+gN34 1E4cqcz4rM2pE6bic9/2Y9RXFwQDk46c57YFsPNQuhR5aJulgC9pyI5rUUXE2k8z86lI 0Nk8CI2KFNbGsTlDqFjwVRbit8mm4gcQ3Gxmg= MIME-Version: 1.0 Received: by 10.42.217.68 with SMTP id hl4mr165259icb.181.1298186788207; Sat, 19 Feb 2011 23:26:28 -0800 (PST) Received: by 10.42.225.193 with HTTP; Sat, 19 Feb 2011 23:26:28 -0800 (PST) In-Reply-To: <20110219105634.1c5e4402@ernst.jennejohn.org> References: <20110219105634.1c5e4402@ernst.jennejohn.org> Date: Sun, 20 Feb 2011 15:26:28 +0800 Message-ID: From: dave jones To: gljennjohn@googlemail.com Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-fs@freebsd.org Subject: Re: msdosfs kernel panic with a broken usb flash drive 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, 20 Feb 2011 07:26:29 -0000 Sorry, I don't have a kernel crash dump, but the ddb trace is something like: msdosfs_setattr()+0x.... The machine is running is 9.0 -current. On Sat, Feb 19, 2011 at 5:56 PM, Gary Jennejohn wrote: > On Sat, 19 Feb 2011 12:42:48 +0800 > dave jones wrote: > >> Recently I have two broken USB thumb drives. I tried to mount /dev/da0s1 >> by using mount_msdosfs /dev/da0s1 /mnt, and I got the kernel panic. >> I tried another broken usb drive, the result is the same, kernel panic. >> I also tried it on Linux using "mount -t /dev/sdb1 /mnt", no panic. >> >> Does it make sense that mounting broken USB drives would cause the >> kernel panic? >> Any idea how to solve this issue? thank you. >> > > Without back trace from ddb or a kernel crash dump it would a little > difficult for anyone to provide an intelligent answer. > > -- > Gary Jennejohn > From owner-freebsd-fs@FreeBSD.ORG Sun Feb 20 11:25:46 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BFE7C106566C; Sun, 20 Feb 2011 11:25:46 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 2EE6E8FC08; Sun, 20 Feb 2011 11:25:45 +0000 (UTC) Received: by wwf26 with SMTP id 26so5073926wwf.31 for ; Sun, 20 Feb 2011 03:25:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=JHjUVn0WlSz/LEtaGRacyKpRNNQpPJ3o6sXZkga7uVU=; b=ZrmF6WjQV5TmQlrG2d+ZiPcg1/2MFHudKqaG7LAhHn9Ey26vzlq8t5tu25XfdzN1Iu j4Jlsl9lGbtMxCEUMS5JK2I0oCgTuL9tQMlFZGJ8b5H6laVqoNLbsFciSEDnMKdBoMh7 lXehtk8Kg8zzsCh97xmOmTUiQfE/UaaRSzPBs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=TFcKCTvrm8X1kNiqp8w2FO+nxPm6TPEL47if7Cugm5qS5yPGjwLldF+TJyZayYxm+T wLZBb2k2zB5mdTzaZq4fHjFITySsVMMvE916pD4Cr+Nyo0Xxd4dNPZBDs3QgFBmgcwxz 5LpNqgFKsHEwxrMm/APB6iMiVyCgeGb2MhqWI= MIME-Version: 1.0 Received: by 10.216.56.65 with SMTP id l43mr1074459wec.113.1298201144514; Sun, 20 Feb 2011 03:25:44 -0800 (PST) Received: by 10.216.80.147 with HTTP; Sun, 20 Feb 2011 03:25:44 -0800 (PST) In-Reply-To: References: <4D5DD580.9040701@freebsd.org> Date: Sun, 20 Feb 2011 11:25:44 +0000 Message-ID: From: krad To: Lawrence Stewart Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-fs@freebsd.org Subject: Re: zfs boot on 4k drives in -STABLE 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, 20 Feb 2011 11:25:46 -0000 On 19 February 2011 10:55, krad wrote: > On 18 February 2011 02:12, Lawrence Stewart wrote: >> On 02/17/11 20:30, krad wrote: >>> Hi, >>> >>> What is the current state of zfs booting of a 4k aligned drive >>> (ashift=12)? I have tried the patch in pr153695 but it wont apply >>> cleanly to stable as I think it is meant for current. Is one going to >>> be made available for STABLE at any point? >> >> It works fine. Use the gptzfsboot and zfsloader from here and you're >> good to go - no patches or anything else required: >> >> http://people.freebsd.org/~pjd/zfsboot/ >> >> Cheers, >> Lawrence >> > > > thanks for the advice ill give it a go > well the binary versions didnt seem to work. The drive is 4k aligned apart from the boot partition. Surely this wouldnt have an affect though would it? # gpart show ad7 => 34 3907029101 ad7 GPT (1.8T) 34 128 1 freebsd-boot (64K) 162 6 - free - (3.0K) 168 6291456 2 freebsd-swap (3.0G) 6291624 3900213229 3 freebsd-zfs (1.8T) 3906504853 524282 4 freebsd-ufs (256M) From owner-freebsd-fs@FreeBSD.ORG Sun Feb 20 09:38:15 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8F321106564A for ; Sun, 20 Feb 2011 09:38:15 +0000 (UTC) (envelope-from kellydeanch@yahoo.com) Received: from nm2.bullet.mail.ne1.yahoo.com (nm2.bullet.mail.ne1.yahoo.com [98.138.90.65]) by mx1.freebsd.org (Postfix) with SMTP id 3FDEF8FC0A for ; Sun, 20 Feb 2011 09:38:14 +0000 (UTC) Received: from [98.138.90.49] by nm2.bullet.mail.ne1.yahoo.com with NNFMP; 20 Feb 2011 09:25:29 -0000 Received: from [98.138.89.252] by tm2.bullet.mail.ne1.yahoo.com with NNFMP; 20 Feb 2011 09:25:29 -0000 Received: from [127.0.0.1] by omp1044.mail.ne1.yahoo.com with NNFMP; 20 Feb 2011 09:25:29 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 664615.88442.bm@omp1044.mail.ne1.yahoo.com Received: (qmail 36052 invoked by uid 60001); 20 Feb 2011 09:25:29 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1298193929; bh=qAJaGhXFDQwfApf71iCpvgg3e8s9ZAsZsPle/RgJk6c=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=dLdZICskW07rfxQXWBxRH6jeShiqjga3Rlq8y7qQ9mSI+OIl+Xa70vaP1UG4Bp54ns0+0V9/iegmQ80EIJbqMadYo446tH5mktj4RdLaQ9GymAcyXOekevro+jhLuk3bTqBiQ/9/QJu3Ct6WtPjv8IEw5gLEoZ0q9iwhHPvpdkg= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=FgIUuKvZAhDPmNL+0fV6iyhqYcxLQaIod1TirCNPfpNGhryAd0zpKxC7hQ3CnmD8cU+nUDQVx4ebGTu36gx6KH35OlpAEOCZqr37ravlfgsRhsy9t9hdU/geJeW5hPYdlJuInbH0HXAaGqSfD1EpDT060fYLCdbWsmihxYYZ3h8=; Message-ID: <457880.36028.qm@web121501.mail.ne1.yahoo.com> X-YMail-OSG: tqz51WIVM1mFv3uHXYf1mUp6Az0DGUzeP30kfWJ_AvyC0s8 RFVRu4js5HosfsCgVo6aNaNH6t2X03O6CnT8nMscpFTWAlzkquwEkxKnGWX5 UBVe5uUrvT66TpO0hhv1ADWHwF1b2FepJsGCksvTw6aTPqsfzyyRIRMuIqlS yhu_bYBhKkCfYpyZOX8Cg_qSQqhbHQbbNosmJ1Z0a_BWhZJKwW7xMKvciKC7 dO5VsUUwjBTUPL6x0xsvXZE9kqA-- Received: from [173.13.165.123] by web121501.mail.ne1.yahoo.com via HTTP; Sun, 20 Feb 2011 01:25:29 PST X-Mailer: YahooMailClassic/11.4.20 YahooMailWebService/0.8.109.292656 Date: Sun, 20 Feb 2011 01:25:29 -0800 (PST) From: Kelly Dean To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailman-Approved-At: Sun, 20 Feb 2011 14:19:50 +0000 Subject: Why is procfs deprecated in favor of procstat? 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, 20 Feb 2011 09:38:15 -0000 http://ivoras.sharanet.org/freebsd/freebsd8.html says that procfs is deprecated in favor of procstat. But Plan 9 says that procfs is the right way to do things. I can't find any explanation why it's deprecated in FreeBSD. From owner-freebsd-fs@FreeBSD.ORG Sun Feb 20 15:49:06 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8AFC31065670; Sun, 20 Feb 2011 15:49:06 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id F20EF8FC1F; Sun, 20 Feb 2011 15:49:05 +0000 (UTC) Received: by wwf26 with SMTP id 26so5194781wwf.31 for ; Sun, 20 Feb 2011 07:49:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=9KeomXdyqkwaFm/4R7F7hotMybTYWe/6vpyFr0VPoFk=; b=Cb3FOCJ48ASF03v5+E8YNJjv43+Fk7PYAOjxDCsrCpCb5orvvd5iNkg+a9/te3AwSj SJKsAmrjaOAgcQxuQNvuGhMhmasb27rfL/IKCqi+/EzEox2O9ciJo+n4TbAL5WNF97Hz WA98eSCNNrD5ATIkdZhr6JRXD6jCu4cXX1mos= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=CWItC2u1S1itkuCVpncEoegqMRR7z7mneaeRC51/DnH4uNA3F17OjdqGBgozd4EJTW L/jfojEXLKdSbIgYjIwbbx3uswGOGzGFdSvrv1YhzQcrt8dyJJujpHM7/yMegmJU2Nby 89RXwxyPAnS5sJwsJ8uxfSdfiHevIS9Xaq4Es= MIME-Version: 1.0 Received: by 10.216.56.65 with SMTP id l43mr1216956wec.113.1298216944807; Sun, 20 Feb 2011 07:49:04 -0800 (PST) Received: by 10.216.80.147 with HTTP; Sun, 20 Feb 2011 07:49:04 -0800 (PST) Date: Sun, 20 Feb 2011 15:49:04 +0000 Message-ID: From: krad To: Lawrence Stewart Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-fs@freebsd.org" Subject: yRe: zfs boot on 4k drives in -STABLE 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, 20 Feb 2011 15:49:06 -0000 U On Sunday, 20 February 2011, krad wrote: > On 19 February 2011 10:55, krad wrote: >> On 18 February 2011 02:12, Lawrence Stewart wrote= : >>> On 02/17/11 20:30, krad wrote: >>>> Hi, >>>> >>>> What is the current state of zfs booting of a 4k aligned drive >>>> (ashift=3D12)? I have tried the patch in pr153695 but it wont apply >>>> cleanly to stable as I think it is meant for current. Is one going to >>>> be made available for STABLE at any point? >>> >>> It works fine. Use the gptzfsboot and zfsloader from here and you're >>> good to go - no patches or anything else required: >>> >>> http://people.freebsd.org/~pjd/zfsboot/ >>> >>> Cheers, >>> Lawrence >>> >> >> >> thanks for the advice ill give it a go >> > > well the binary versions didnt seem to work. The drive is 4k aligned > apart from the boot partition. Surely this wouldnt have an affect > though would it? > > # gpart show ad7 > =3D> =A0 =A0 =A0 =A034 =A03907029101 =A0ad7 =A0GPT =A0(1.8T) > =A0 =A0 =A0 =A0 =A034 =A0 =A0 =A0 =A0 128 =A0 =A01 =A0freebsd-boot =A0(6= 4K) > =A0 =A0 =A0 =A0 162 =A0 =A0 =A0 =A0 =A0 6 =A0 =A0 =A0 - free - =A0(3.0K) > =A0 =A0 =A0 =A0 168 =A0 =A0 6291456 =A0 =A02 =A0freebsd-swap =A0(3.0G) > =A0 =A0 6291624 =A03900213229 =A0 =A03 =A0freebsd-zfs =A0(1.8T) > =A03906504853 =A0 =A0 =A0524282 =A0 =A04 =A0freebsd-ufs =A0(256M) as I thought realigning the boot partition didn't help > From owner-freebsd-fs@FreeBSD.ORG Mon Feb 21 09:13:10 2011 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 058611065670; Mon, 21 Feb 2011 09:13:10 +0000 (UTC) (envelope-from brucec@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id CE5828FC14; Mon, 21 Feb 2011 09:13:09 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1L9D9T6054930; Mon, 21 Feb 2011 09:13:09 GMT (envelope-from brucec@freefall.freebsd.org) Received: (from brucec@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1L9D9GU054926; Mon, 21 Feb 2011 09:13:09 GMT (envelope-from brucec) Date: Mon, 21 Feb 2011 09:13:09 GMT Message-Id: <201102210913.p1L9D9GU054926@freefall.freebsd.org> To: simon@comsys.ntu-kpi.kiev.ua, brucec@FreeBSD.org, freebsd-fs@FreeBSD.org, rmacklem@FreeBSD.org From: brucec@FreeBSD.org Cc: Subject: Re: kern/146375: [nfs] [patch] Typos in macro variables names in sys/fs/nfs/*.h 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: Mon, 21 Feb 2011 09:13:10 -0000 Synopsis: [nfs] [patch] Typos in macro variables names in sys/fs/nfs/*.h State-Changed-From-To: open->patched State-Changed-By: brucec State-Changed-When: Mon Feb 21 09:12:24 UTC 2011 State-Changed-Why: MFC reminder. Responsible-Changed-From-To: freebsd-fs->rmacklem Responsible-Changed-By: brucec Responsible-Changed-When: Mon Feb 21 09:12:24 UTC 2011 Responsible-Changed-Why: MFC reminder. http://www.freebsd.org/cgi/query-pr.cgi?pr=146375 From owner-freebsd-fs@FreeBSD.ORG Mon Feb 21 11:06:59 2011 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6070F1065705 for ; Mon, 21 Feb 2011 11:06:59 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 32D688FC21 for ; Mon, 21 Feb 2011 11:06:59 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1LB6x52075698 for ; Mon, 21 Feb 2011 11:06:59 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1LB6wRH075696 for freebsd-fs@FreeBSD.org; Mon, 21 Feb 2011 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 21 Feb 2011 11:06:58 GMT Message-Id: <201102211106.p1LB6wRH075696@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-fs@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-fs@FreeBSD.org 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: Mon, 21 Feb 2011 11:06:59 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/154681 fs [zfs] [panic] panic with FreeBSD-8 STABLE o kern/154491 fs [smbfs] smb_co_lock: recursive lock for object 1 o kern/154447 fs [zfs] [panic] Occasional panics - solaris assert somew f kern/154228 fs [md] md getting stuck in wdrain state o kern/153996 fs [zfs] zfs root mount error while kernel is not located o kern/153847 fs [nfs] [panic] Kernel panic from incorrect m_free in nf o kern/153753 fs [zfs] ZFS v15 - grammatical error when attempting to u o kern/153716 fs [zfs] zpool scrub time remaining is incorrect o kern/153695 fs [patch] [zfs] Booting from zpool created on 4k-sector o kern/153680 fs [xfs] 8.1 failing to mount XFS partitions o kern/153552 fs [zfs] zfsboot from 8.2-RC1 freeze at boot time o kern/153520 fs [zfs] Boot from GPT ZFS root on HP BL460c G1 unstable o kern/153418 fs [zfs] [panic] Kernel Panic occurred writing to zfs vol o kern/153351 fs [zfs] locking directories/files in ZFS o bin/153258 fs [patch][zfs] creating ZVOLs requires `refreservation' s kern/153173 fs [zfs] booting from a gzip-compressed dataset doesn't w o kern/153126 fs [zfs] vdev failure, zpool=peegel type=vdev.too_small p kern/152488 fs [tmpfs] [patch] mtime of file updated when only inode o kern/152079 fs [msdosfs] [patch] Small cleanups from the other NetBSD o kern/152022 fs [nfs] nfs service hangs with linux client [regression] o kern/151942 fs [zfs] panic during ls(1) zfs snapshot directory o kern/151905 fs [zfs] page fault under load in /sbin/zfs o kern/151845 fs [smbfs] [patch] smbfs should be upgraded to support Un o bin/151713 fs [patch] Bug in growfs(8) with respect to 32-bit overfl o kern/151648 fs [zfs] disk wait bug o kern/151629 fs [fs] [patch] Skip empty directory entries during name o kern/151330 fs [zfs] will unshare all zfs filesystem after execute a o kern/151326 fs [nfs] nfs exports fail if netgroups contain duplicate o kern/151251 fs [ufs] Can not create files on filesystem with heavy us o kern/151226 fs [zfs] can't delete zfs snapshot o kern/151111 fs [zfs] vnodes leakage during zfs unmount o kern/150503 fs [zfs] ZFS disks are UNAVAIL and corrupted after reboot o kern/150501 fs [zfs] ZFS vdev failure vdev.bad_label on amd64 o kern/150390 fs [zfs] zfs deadlock when arcmsr reports drive faulted o kern/150336 fs [nfs] mountd/nfsd became confused; refused to reload n o kern/150207 fs zpool(1): zpool import -d /dev tries to open weird dev o kern/149208 fs mksnap_ffs(8) hang/deadlock o kern/149173 fs [patch] [zfs] make OpenSolaris installa f kern/149022 fs [hang] File system operations hangs with suspfs state o kern/149015 fs [zfs] [patch] misc fixes for ZFS code to build on Glib o kern/149014 fs [zfs] [patch] declarations in ZFS libraries/utilities o kern/149013 fs [zfs] [patch] make ZFS makefiles use the libraries fro o kern/148504 fs [zfs] ZFS' zpool does not allow replacing drives to be o kern/148490 fs [zfs]: zpool attach - resilver bidirectionally, and re o kern/148368 fs [zfs] ZFS hanging forever on 8.1-PRERELEASE o bin/148296 fs [zfs] [loader] [patch] Very slow probe in /usr/src/sys o kern/148204 fs [nfs] UDP NFS causes overload o kern/148138 fs [zfs] zfs raidz pool commands freeze o kern/147903 fs [zfs] [panic] Kernel panics on faulty zfs device o kern/147881 fs [zfs] [patch] ZFS "sharenfs" doesn't allow different " o kern/147790 fs [zfs] zfs set acl(mode|inherit) fails on existing zfs o kern/147560 fs [zfs] [boot] Booting 8.1-PRERELEASE raidz system take o kern/147420 fs [ufs] [panic] ufs_dirbad, nullfs, jail panic (corrupt o kern/146941 fs [zfs] [panic] Kernel Double Fault - Happens constantly o kern/146786 fs [zfs] zpool import hangs with checksum errors o kern/146708 fs [ufs] [panic] Kernel panic in softdep_disk_write_compl o kern/146528 fs [zfs] Severe memory leak in ZFS on i386 o kern/146502 fs [nfs] FreeBSD 8 NFS Client Connection to Server s kern/145712 fs [zfs] cannot offline two drives in a raidz2 configurat o kern/145411 fs [xfs] [panic] Kernel panics shortly after mounting an o bin/145309 fs bsdlabel: Editing disk label invalidates the whole dev o kern/145272 fs [zfs] [panic] Panic during boot when accessing zfs on o kern/145246 fs [ufs] dirhash in 7.3 gratuitously frees hashes when it o kern/145238 fs [zfs] [panic] kernel panic on zpool clear tank o kern/145229 fs [zfs] Vast differences in ZFS ARC behavior between 8.0 o kern/145189 fs [nfs] nfsd performs abysmally under load o kern/144929 fs [ufs] [lor] vfs_bio.c + ufs_dirhash.c o kern/144458 fs [nfs] [patch] nfsd fails as a kld p kern/144447 fs [zfs] sharenfs fsunshare() & fsshare_main() non functi o kern/144416 fs [panic] Kernel panic on online filesystem optimization s kern/144415 fs [zfs] [panic] kernel panics on boot after zfs crash o kern/144234 fs [zfs] Cannot boot machine with recent gptzfsboot code o kern/143825 fs [nfs] [panic] Kernel panic on NFS client o bin/143572 fs [zfs] zpool(1): [patch] The verbose output from iostat o kern/143212 fs [nfs] NFSv4 client strange work ... o kern/143184 fs [zfs] [lor] zfs/bufwait LOR o kern/142914 fs [zfs] ZFS performance degradation over time o kern/142878 fs [zfs] [vfs] lock order reversal o kern/142597 fs [ext2fs] ext2fs does not work on filesystems with real o kern/142489 fs [zfs] [lor] allproc/zfs LOR o kern/142466 fs Update 7.2 -> 8.0 on Raid 1 ends with screwed raid [re o kern/142401 fs [ntfs] [patch] Minor updates to NTFS from NetBSD o kern/142306 fs [zfs] [panic] ZFS drive (from OSX Leopard) causes two o kern/142068 fs [ufs] BSD labels are got deleted spontaneously o kern/141897 fs [msdosfs] [panic] Kernel panic. msdofs: file name leng o kern/141463 fs [nfs] [panic] Frequent kernel panics after upgrade fro o kern/141305 fs [zfs] FreeBSD ZFS+sendfile severe performance issues ( o kern/141091 fs [patch] [nullfs] fix panics with DIAGNOSTIC enabled o kern/141086 fs [nfs] [panic] panic("nfs: bioread, not dir") on FreeBS o kern/141010 fs [zfs] "zfs scrub" fails when backed by files in UFS2 o kern/140888 fs [zfs] boot fail from zfs root while the pool resilveri o kern/140661 fs [zfs] [patch] /boot/loader fails to work on a GPT/ZFS- o kern/140640 fs [zfs] snapshot crash o kern/140134 fs [msdosfs] write and fsck destroy filesystem integrity o kern/140068 fs [smbfs] [patch] smbfs does not allow semicolon in file o kern/139725 fs [zfs] zdb(1) dumps core on i386 when examining zpool c o kern/139715 fs [zfs] vfs.numvnodes leak on busy zfs p bin/139651 fs [nfs] mount(8): read-only remount of NFS volume does n o kern/139597 fs [patch] [tmpfs] tmpfs initializes va_gen but doesn't u o kern/139564 fs [zfs] [panic] 8.0-RC1 - Fatal trap 12 at end of shutdo o kern/139407 fs [smbfs] [panic] smb mount causes system crash if remot o kern/138790 fs [zfs] ZFS ceases caching when mem demand is high o kern/138662 fs [panic] ffs_blkfree: freeing free block o kern/138421 fs [ufs] [patch] remove UFS label limitations o kern/138202 fs mount_msdosfs(1) see only 2Gb o kern/136968 fs [ufs] [lor] ufs/bufwait/ufs (open) o kern/136945 fs [ufs] [lor] filedesc structure/ufs (poll) o kern/136944 fs [ffs] [lor] bufwait/snaplk (fsync) o kern/136873 fs [ntfs] Missing directories/files on NTFS volume o kern/136865 fs [nfs] [patch] NFS exports atomic and on-the-fly atomic p kern/136470 fs [nfs] Cannot mount / in read-only, over NFS o kern/135546 fs [zfs] zfs.ko module doesn't ignore zpool.cache filenam o kern/135469 fs [ufs] [panic] kernel crash on md operation in ufs_dirb o kern/135050 fs [zfs] ZFS clears/hides disk errors on reboot o kern/134491 fs [zfs] Hot spares are rather cold... o kern/133676 fs [smbfs] [panic] umount -f'ing a vnode-based memory dis o kern/133614 fs [panic] panic: ffs_truncate: read-only filesystem o kern/133174 fs [msdosfs] [patch] msdosfs must support utf-encoded int o kern/132960 fs [ufs] [panic] panic:ffs_blkfree: freeing free frag o kern/132397 fs reboot causes filesystem corruption (failure to sync b o kern/132331 fs [ufs] [lor] LOR ufs and syncer o kern/132237 fs [msdosfs] msdosfs has problems to read MSDOS Floppy o kern/132145 fs [panic] File System Hard Crashes o kern/131441 fs [unionfs] [nullfs] unionfs and/or nullfs not combineab o kern/131360 fs [nfs] poor scaling behavior of the NFS server under lo o kern/131342 fs [nfs] mounting/unmounting of disks causes NFS to fail o bin/131341 fs makefs: error "Bad file descriptor" on the mount poin o kern/130920 fs [msdosfs] cp(1) takes 100% CPU time while copying file o kern/130210 fs [nullfs] Error by check nullfs o kern/129760 fs [nfs] after 'umount -f' of a stale NFS share FreeBSD l o kern/129488 fs [smbfs] Kernel "bug" when using smbfs in smbfs_smb.c: o kern/129231 fs [ufs] [patch] New UFS mount (norandom) option - mostly o kern/129152 fs [panic] non-userfriendly panic when trying to mount(8) o kern/127787 fs [lor] [ufs] Three LORs: vfslock/devfs/vfslock, ufs/vfs o bin/127270 fs fsck_msdosfs(8) may crash if BytesPerSec is zero o kern/127029 fs [panic] mount(8): trying to mount a write protected zi o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file o kern/125895 fs [ffs] [panic] kernel: panic: ffs_blkfree: freeing free s kern/125738 fs [zfs] [request] SHA256 acceleration in ZFS o kern/123939 fs [msdosfs] corrupts new files o kern/122380 fs [ffs] ffs_valloc:dup alloc (Soekris 4801/7.0/USB Flash o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o bin/121898 fs [nullfs] pwd(1)/getcwd(2) fails with Permission denied o bin/121366 fs [zfs] [patch] Automatic disk scrubbing from periodic(8 o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha f kern/120991 fs [panic] [ffs] [snapshot] System crashes when manipulat o kern/120483 fs [ntfs] [patch] NTFS filesystem locking changes o kern/120482 fs [ntfs] [patch] Sync style changes between NetBSD and F o kern/118912 fs [2tb] disk sizing/geometry problem with large array o kern/118713 fs [minidump] [patch] Display media size required for a k o bin/118249 fs [ufs] mv(1): moving a directory changes its mtime o kern/118107 fs [ntfs] [panic] Kernel panic when accessing a file at N o kern/117954 fs [ufs] dirhash on very large directories blocks the mac o bin/117315 fs [smbfs] mount_smbfs(8) and related options can't mount o kern/117314 fs [ntfs] Long-filename only NTFS fs'es cause kernel pani o kern/117158 fs [zfs] zpool scrub causes panic if geli vdevs detach on o bin/116980 fs [msdosfs] [patch] mount_msdosfs(8) resets some flags f o conf/116931 fs lack of fsck_cd9660 prevents mounting iso images with p kern/116608 fs [msdosfs] [patch] msdosfs fails to check mount options o kern/116583 fs [ffs] [hang] System freezes for short time when using o kern/116170 fs [panic] Kernel panic when mounting /tmp o bin/115361 fs [zfs] mount(8) gets into a state where it won't set/un o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o kern/113852 fs [smbfs] smbfs does not properly implement DFS referral o bin/113838 fs [patch] [request] mount(8): add support for relative p o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/111843 fs [msdosfs] Long Names of files are incorrectly created o kern/111782 fs [ufs] dump(8) fails horribly for large filesystems s bin/111146 fs [2tb] fsck(8) fails on 6T filesystem o kern/109024 fs [msdosfs] [iconv] mount_msdosfs: msdosfs_iconv: Operat o kern/109010 fs [msdosfs] can't mv directory within fat32 file system o bin/107829 fs [2TB] fdisk(8): invalid boundary checking in fdisk / w o kern/106107 fs [ufs] left-over fsck_snapshot after unfinished backgro o kern/106030 fs [ufs] [panic] panic in ufs from geom when a dead disk o kern/104406 fs [ufs] Processes get stuck in "ufs" state under persist o kern/104133 fs [ext2fs] EXT2FS module corrupts EXT2/3 filesystems o kern/103035 fs [ntfs] Directories in NTFS mounted disc images appear o kern/101324 fs [smbfs] smbfs sometimes not case sensitive when it's s o kern/99290 fs [ntfs] mount_ntfs ignorant of cluster sizes s bin/97498 fs [request] newfs(8) has no option to clear the first 12 o kern/97377 fs [ntfs] [patch] syntax cleanup for ntfs_ihash.c o kern/95222 fs [cd9660] File sections on ISO9660 level 3 CDs ignored o kern/94849 fs [ufs] rename on UFS filesystem is not atomic o bin/94810 fs fsck(8) incorrectly reports 'file system marked clean' o kern/94769 fs [ufs] Multiple file deletions on multi-snapshotted fil o kern/94733 fs [smbfs] smbfs may cause double unlock o kern/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D o kern/92272 fs [ffs] [hang] Filling a filesystem while creating a sna o kern/91134 fs [smbfs] [patch] Preserve access and modification time a kern/90815 fs [smbfs] [patch] SMBFS with character conversions somet o kern/88657 fs [smbfs] windows client hang when browsing a samba shar o kern/88555 fs [panic] ffs_blkfree: freeing free frag on AMD 64 o kern/88266 fs [smbfs] smbfs does not implement UIO_NOCOPY and sendfi o bin/87966 fs [patch] newfs(8): introduce -A flag for newfs to enabl o kern/87859 fs [smbfs] System reboot while umount smbfs. o kern/86587 fs [msdosfs] rm -r /PATH fails with lots of small files o bin/85494 fs fsck_ffs: unchecked use of cg_inosused macro etc. o kern/80088 fs [smbfs] Incorrect file time setting on NTFS mounted vi o bin/74779 fs Background-fsck checks one filesystem twice and omits o kern/73484 fs [ntfs] Kernel panic when doing `ls` from the client si o bin/73019 fs [ufs] fsck_ufs(8) cannot alloc 607016868 bytes for ino o kern/71774 fs [ntfs] NTFS cannot "see" files on a WinXP filesystem o bin/70600 fs fsck(8) throws files away when it can't grow lost+foun o kern/68978 fs [panic] [ufs] crashes with failing hard disk, loose po o kern/65920 fs [nwfs] Mounted Netware filesystem behaves strange o kern/65901 fs [smbfs] [patch] smbfs fails fsx write/truncate-down/tr o kern/61503 fs [smbfs] mount_smbfs does not work as non-root o kern/55617 fs [smbfs] Accessing an nsmb-mounted drive via a smb expo o kern/51685 fs [hang] Unbounded inode allocation causes kernel to loc o kern/51583 fs [nullfs] [patch] allow to work with devices and socket o kern/36566 fs [smbfs] System reboot with dead smb mount and umount o kern/33464 fs [ufs] soft update inconsistencies after system crash o bin/27687 fs fsck(8) wrapper is not properly passing options to fsc o kern/18874 fs [2TB] 32bit NFS servers export wrong negative values t 218 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Feb 21 12:35:12 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 628BF106566B; Mon, 21 Feb 2011 12:35:12 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id C50408FC08; Mon, 21 Feb 2011 12:35:11 +0000 (UTC) Received: by wyb32 with SMTP id 32so1739509wyb.13 for ; Mon, 21 Feb 2011 04:35:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=OUi3oL0IsjtFGjt0BBUfS6Yxs8YeYklsnVUIvCAeJgI=; b=b6wNR8IP1SxGaJCxwko1OBFNAbW9F/cSdMAz2bZaiS3vKhRsHvq2hcErJtIh/5/p1Y Uk2HLEoOanNEap5Xw43VdSprcibMAEtBRxWTXV3JRny40zHgYFvpKPvGad44jESB4ZHL 8d/zEVEKRyLcz3ZJUUpuaTqaIXK01wJ79MgFc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Cs+EEMwmJukdO7hnK3tX9Jp2EHoznpja0ylRtlQGtO7cGP2CvBQDW7n86BmOwciZLI ru2mnuO6IO3yWmG+rcXy/tWMXBxbkBoOMVWa5RfdM7XA9OnjtDJtv6glXnWZPk+dscCm OgVOuPnA4bf32+K6EhQiMVu2w4g1vbnjwdRzs= MIME-Version: 1.0 Received: by 10.216.178.138 with SMTP id f10mr1059570wem.98.1298291710772; Mon, 21 Feb 2011 04:35:10 -0800 (PST) Received: by 10.216.80.147 with HTTP; Mon, 21 Feb 2011 04:35:10 -0800 (PST) In-Reply-To: References: <4D5DD580.9040701@freebsd.org> Date: Mon, 21 Feb 2011 12:35:10 +0000 Message-ID: From: krad To: Lawrence Stewart Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: zfs boot on 4k drives in -STABLE 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: Mon, 21 Feb 2011 12:35:12 -0000 On 20 February 2011 11:25, krad wrote: > On 19 February 2011 10:55, krad wrote: >> On 18 February 2011 02:12, Lawrence Stewart wrote= : >>> On 02/17/11 20:30, krad wrote: >>>> Hi, >>>> >>>> What is the current state of zfs booting of a 4k aligned drive >>>> (ashift=3D12)? I have tried the patch in pr153695 but it wont apply >>>> cleanly to stable as I think it is meant for current. Is one going to >>>> be made available for STABLE at any point? >>> >>> It works fine. Use the gptzfsboot and zfsloader from here and you're >>> good to go - no patches or anything else required: >>> >>> http://people.freebsd.org/~pjd/zfsboot/ >>> >>> Cheers, >>> Lawrence >>> >> >> >> thanks for the advice ill give it a go >> > > well the binary versions didnt seem to work. The drive is 4k aligned > apart from the boot partition. Surely this wouldnt have an affect > though would it? > > # gpart show ad7 > =3D> =A0 =A0 =A0 =A034 =A03907029101 =A0ad7 =A0GPT =A0(1.8T) > =A0 =A0 =A0 =A0 =A034 =A0 =A0 =A0 =A0 128 =A0 =A01 =A0freebsd-boot =A0(64= K) > =A0 =A0 =A0 =A0 162 =A0 =A0 =A0 =A0 =A0 6 =A0 =A0 =A0 - free - =A0(3.0K) > =A0 =A0 =A0 =A0 168 =A0 =A0 6291456 =A0 =A02 =A0freebsd-swap =A0(3.0G) > =A0 =A0 6291624 =A03900213229 =A0 =A03 =A0freebsd-zfs =A0(1.8T) > =A03906504853 =A0 =A0 =A0524282 =A0 =A04 =A0freebsd-ufs =A0(256M) > after realigning the boot partition it still failed to boot From owner-freebsd-fs@FreeBSD.ORG Mon Feb 21 16:05:43 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 44FBD10656AB for ; Mon, 21 Feb 2011 16:05:43 +0000 (UTC) (envelope-from prvs=026c6f404=Christian.Vogt@haw-hamburg.de) Received: from mx6.haw-public.haw-hamburg.de (mx6.haw-public.haw-hamburg.de [141.22.6.3]) by mx1.freebsd.org (Postfix) with ESMTP id CB5B88FC1A for ; Mon, 21 Feb 2011 16:05:42 +0000 (UTC) Received: from dehawshub01.mailcluster.haw-hamburg.de ([141.22.200.36]) by mail6.is.haw-hamburg.de with ESMTP/TLS/RC4-MD5; 21 Feb 2011 16:55:36 +0100 Received: from dehawscas03.mailcluster.haw-hamburg.de (141.22.200.53) by DEHAWSHUB01.mailcluster.haw-hamburg.de (141.22.200.36) with Microsoft SMTP Server (TLS) id 8.1.358.0; Mon, 21 Feb 2011 16:55:36 +0100 Received: from [172.20.0.45] (141.22.200.55) by haw-mailer.haw-hamburg.de (141.22.200.80) with Microsoft SMTP Server (TLS) id 8.1.358.0; Mon, 21 Feb 2011 16:55:36 +0100 From: Christian Vogt Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 21 Feb 2011 16:55:35 +0100 Message-ID: <2C4EE30F-7731-4B84-ADC6-75C0266863F0@haw-hamburg.de> To: MIME-Version: 1.0 (Apple Message framework v1082) X-Mailer: Apple Mail (2.1082) Cc: Subject: hastd Failover with ucarp 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: Mon, 21 Feb 2011 16:05:43 -0000 Hello!=20 Thanks for the great work, I like this straight-forward FreeBSD a lot = from what I experienced untill now. I used the HAST How-To from = http://wiki.freebsd.org/HAST and it works perfectly if I use "pkill = -USR2 -f 'ucarp -B'" to initiate the failover. The secondary node = becomes primary and the carp-interface is switched over to it.=20 But if I do a hard shutdown of the primary node it doesn't work, the = secondary node doesn't get primary. The ucarp-up script on the secondary = node is executed, but it fails because of the still running secondary = worker process (Secondary process for resource test is still running = after 30 seconds). Is the secondary process expected to end = automatically, when the primary process fails? Thanks for your help Christian= From owner-freebsd-fs@FreeBSD.ORG Mon Feb 21 16:06:25 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9093A1065696 for ; Mon, 21 Feb 2011 16:06:25 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from mail.ijs.si (mail.ijs.si [IPv6:2001:1470:ff80::25]) by mx1.freebsd.org (Postfix) with ESMTP id 0CEBA8FC2A for ; Mon, 21 Feb 2011 16:06:25 +0000 (UTC) Received: from amavis-proxy-ori.ijs.si (localhost [IPv6:::1]) by mail.ijs.si (Postfix) with ESMTP id CAA901D1D9A for ; Mon, 21 Feb 2011 17:06:23 +0100 (CET) Authentication-Results: mail.ijs.si; dkim=pass (1024-bit key) header.i=@ijs.si header.b=CQ/lY4Tl; dkim-adsp=pass DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ijs.si; h= message-id:content-transfer-encoding:content-type:content-type :mime-version:user-agent:date:date:subject:subject:organization :from:from:received:received:received:vbr-info; s=jakla2; t= 1298304380; x=1300896381; bh=GI1paPI3ryNclHAstfF8XUf3UX4HxnX6J2M wn/+2B5w=; b=CQ/lY4Tl8HkVhSSKl99aHgsMr0pXV1n2scAWmjvcY5GrvwMjfWi +ZECrDZzpxLFYFTlMpVCee7A8nLmEhKO0pyvlNZBSBOBgpuqoq5yAuf34ah7YPMs Kd7DJLceLSyhv9oXHOMWg+er3ZbCp0SGUqr7R9ryANR1HYLif6DawMNM= VBR-Info: md=ijs.si; mc=all; mv=dwl.spamhaus.org; X-Virus-Scanned: amavisd-new at ijs.si Received: from mail.ijs.si ([127.0.0.1]) by amavis-proxy-ori.ijs.si (mail.ijs.si [127.0.0.1]) (amavisd-new, port 10012) with ESMTP id Cu0xRJBqgvSg for ; Mon, 21 Feb 2011 17:06:20 +0100 (CET) Received: from edina.ijs.si (unknown [IPv6:2001:1470:ff80:0:2e0:81ff:fe72:51d]) by mail.ijs.si (Postfix) with ESMTP for ; Mon, 21 Feb 2011 17:06:20 +0100 (CET) Received: from neli.ijs.si (neli.ijs.si [193.2.4.95]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by edina.ijs.si (Postfix) with ESMTPSA id A201022F229 for ; Mon, 21 Feb 2011 17:06:18 +0100 (CET) From: Mark Martinec Organization: J. Stefan Institute To: freebsd-fs@freebsd.org Date: Mon, 21 Feb 2011 17:06:18 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.1-RELEASE-p2; KDE/4.5.5; amd64; ; ) MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201102211706.18084.Mark.Martinec+freebsd@ijs.si> Subject: ftruncate under ZFS requires W file access permission, instead of testing file open mode (O_RDWR) 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: Mon, 21 Feb 2011 16:06:25 -0000 I filed this as: http://www.freebsd.org/cgi/query-pr.cgi?pr=154873 under a 'standards' category - should be assigned to [freebsd-fs]: standards/154873: ZFS violates POSIX on open/O_CREAT -> ftruncate Description: POSIX.1-2008 requires that the third argument to open(2) on O_CREAT does not affect whether the file is open for reading, writing, or for both. A subsequent ftruncate should not depend on access permission bits of the file, but solely on the read/write flags specified on the open(2). The bug affects a mailer Postfix, which reports a permission problem on ftruncate, affecting the smtpd service when option speed_adjust is requested. As the problem is in the file system violating a POSIX specification and not in the application, it is unlikely that the program will be modified. Reproducible on: FreeBSD 8.1-RELEASE-p2, ZFS: pool version 14, ZFS version 3 as well as on: FreeBSD 8.2-RC3, ZFS: pool version 15, ZFS version 4 How-To-Repeat: Run the following test program. It will report: Error truncating: Permission denied when (cwd) on a ZFS file system, but will pass clean when on UFS or on some other file system. #include #include #include int main(int argc, char *argv[]) { const char fname[] = "truncate-posix-test.tmp"; /* POSIX.1-2008: ( http://www.opengroup.org/onlinepubs/9699919799/ ) * open() [...] O_CREAT [...] The file status flags and file * access modes of the open file description shall be set according * to the value of oflag. [...] The argument following the oflag * argument does not affect whether the file is open for reading, * writing, or for both. * * In other words, read/write access is controlled with the * O_RDWR flags, not the read/write permissions argument. * * Create a file with mode 0, i.e. all access permission bits off: */ int fd = open(fname, O_CREAT|O_RDWR|O_EXCL, 0); if (fd < 0) { perror("Error creating file"); return 1; } if (unlink(fname) < 0) perror("Error unlinking"); /* ftruncate should succeed, * it must not depend on access permission bits, its rights * should solely be governed by an O_RDWR file access flag. * * This FAILS on a ZFS file system, reporting "Permission denied"! */ if (ftruncate(fd,0) < 0) perror("Error truncating"); if (close(fd) < 0) perror("Error closing"); return 0; } Fix: Fix unknown. Work around by not using ZFS, or by allowing less strict access permission bits on open(2) - which may be hard to achieve if code is buried inside some application. Mark From owner-freebsd-fs@FreeBSD.ORG Mon Feb 21 17:07:55 2011 Return-Path: Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC9601065672 for ; Mon, 21 Feb 2011 17:07:55 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id 5CE138FC18 for ; Mon, 21 Feb 2011 17:07:55 +0000 (UTC) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.3/8.14.3) with ESMTP id p1LH7cw5075661; Mon, 21 Feb 2011 18:07:53 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id p1LH7c8n075660; Mon, 21 Feb 2011 18:07:38 +0100 (CET) (envelope-from olli) Date: Mon, 21 Feb 2011 18:07:38 +0100 (CET) Message-Id: <201102211707.p1LH7c8n075660@lurza.secnetix.de> From: Oliver Fromme To: freebsd-fs@FreeBSD.ORG, kellydeanch@yahoo.com In-Reply-To: <457880.36028.qm@web121501.mail.ne1.yahoo.com> X-Newsgroups: list.freebsd-fs User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.4-PRERELEASE-20080904 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.3.5 (lurza.secnetix.de [127.0.0.1]); Mon, 21 Feb 2011 18:07:53 +0100 (CET) Cc: Subject: Re: Why is procfs deprecated in favor of procstat? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-fs@FreeBSD.ORG, kellydeanch@yahoo.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Feb 2011 17:07:55 -0000 Kelly Dean wrote: > http://ivoras.sharanet.org/freebsd/freebsd8.html says that > procfs is deprecated in favor of procstat. But Plan 9 says > that procfs is the right way to do things. Linux says the same. But it's irrelevant what they say. FreeBSD is not Plan 9, and FreeBSD is not Linux. Procfs has a long history of security vulnerabilities and other problems. I do not mount procfs on most machines I'm responsible for, especially not on machines that have user accounts or services that are not restricted to jails. I also think it is inefficient to let the kernel render data to ASCII, and then have userland tools parse that ASCII data again. That's ridiculous. There is no sane reason for putting kernel data as ASCII text into a pseudo file system. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "anyone new to programming should be kept as far from C++ as possible; actually showing the stuff should be considered a criminal offence" -- Jacek Generowicz From owner-freebsd-fs@FreeBSD.ORG Mon Feb 21 17:38:52 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B29A71065673 for ; Mon, 21 Feb 2011 17:38:52 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 6DC7C8FC19 for ; Mon, 21 Feb 2011 17:38:52 +0000 (UTC) Received: by ywf9 with SMTP id 9so297795ywf.13 for ; Mon, 21 Feb 2011 09:38:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=hYN4Tpqe5exzsZghWfN/XMkK7Px1M0HqZqpXdsiIUBE=; b=p4mSDLzVyhXaLmV1l54mQuclFxFGIoUck0e5SqlZ5HXEGlWICFIVihg8G6kjv7IAYw OatXjWDkm2L9fE9Td1KWwBtN7KXy3egp7VObr/4JIU8+IA6UCJ/nEqD653yu90k0707G V9a3/c/R04raWCHg1CZ9U4uuoOsnUHlx79M2M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Vn5CPeqm7OSFedIZZ4jdtLFPKGe/rzFXTPFUl9bzqnBafS3ubd64AiedlgtEFknPbx /03SIgQn7n/a/dRRY9L9TKChVEKt2kGvi5bjWKkCB9UY1eysLHSJSbFmO0D5bYPVX/ro IqYo2wDG+0IwR71jFNt84zr036i5M9gZNTRRw= MIME-Version: 1.0 Received: by 10.90.52.5 with SMTP id z5mr2165613agz.181.1298309931059; Mon, 21 Feb 2011 09:38:51 -0800 (PST) Received: by 10.90.73.6 with HTTP; Mon, 21 Feb 2011 09:38:51 -0800 (PST) In-Reply-To: <2C4EE30F-7731-4B84-ADC6-75C0266863F0@haw-hamburg.de> References: <2C4EE30F-7731-4B84-ADC6-75C0266863F0@haw-hamburg.de> Date: Mon, 21 Feb 2011 09:38:51 -0800 Message-ID: From: Freddie Cash To: Christian Vogt Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: hastd Failover with ucarp 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: Mon, 21 Feb 2011 17:38:52 -0000 On Mon, Feb 21, 2011 at 7:55 AM, Christian Vogt wrote: > Thanks for the great work, I like this straight-forward FreeBSD a lot fro= m what I experienced untill now. I used the HAST How-To from http://wiki.fr= eebsd.org/HAST and it works perfectly if I use "pkill -USR2 -f 'ucarp -B'" = to initiate the failover. The secondary node becomes primary and the carp-i= nterface is switched over to it. > > But if I do a hard shutdown of the primary node it doesn't work, the seco= ndary node doesn't get primary. The ucarp-up script on the secondary node i= s executed, but it fails because of the still running secondary worker proc= ess =C2=A0(Secondary process for resource test is still running after 30 se= conds). Is the secondary process expected to end automatically, when the pr= imary process fails? > > Thanks for your help Does it work correctly if you use the built-in carp(4) + devd(8) instead of the port for ucarp? That will narrow down whether it's an issue with ucarp or with hastd(8). Personally, I prefer to use the tools that ship with FreeBSD, as it gives it a more integrated feel. http://blather.michaelwlucas.com/?p=3D241 Has some pre-configured scripts for hooking into devd.conf(5) to glue together carp(4) and hastd(8). Works for ZFS and UFS. --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-fs@FreeBSD.ORG Mon Feb 21 17:41:05 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C0A64106566C for ; Mon, 21 Feb 2011 17:41:05 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [76.96.62.32]) by mx1.freebsd.org (Postfix) with ESMTP id 6D0888FC0A for ; Mon, 21 Feb 2011 17:41:05 +0000 (UTC) Received: from omta04.westchester.pa.mail.comcast.net ([76.96.62.35]) by qmta03.westchester.pa.mail.comcast.net with comcast id Aheg1g0040ldTLk53hh5Nv; Mon, 21 Feb 2011 17:41:05 +0000 Received: from koitsu.dyndns.org ([98.248.33.18]) by omta04.westchester.pa.mail.comcast.net with comcast id Ahh21g0070PUQVN3Qhh3dV; Mon, 21 Feb 2011 17:41:04 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id C9B7C9B422; Mon, 21 Feb 2011 09:41:00 -0800 (PST) Date: Mon, 21 Feb 2011 09:41:00 -0800 From: Jeremy Chadwick To: freebsd-fs@FreeBSD.ORG, kellydeanch@yahoo.com Message-ID: <20110221174100.GA77744@icarus.home.lan> References: <457880.36028.qm@web121501.mail.ne1.yahoo.com> <201102211707.p1LH7c8n075660@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201102211707.p1LH7c8n075660@lurza.secnetix.de> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Subject: Re: Why is procfs deprecated in favor of procstat? 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: Mon, 21 Feb 2011 17:41:05 -0000 On Mon, Feb 21, 2011 at 06:07:38PM +0100, Oliver Fromme wrote: > Kelly Dean wrote: > > http://ivoras.sharanet.org/freebsd/freebsd8.html says that > > procfs is deprecated in favor of procstat. But Plan 9 says > > that procfs is the right way to do things. > > Linux says the same. But it's irrelevant what they say. > FreeBSD is not Plan 9, and FreeBSD is not Linux. > > Procfs has a long history of security vulnerabilities and > other problems. I do not mount procfs on most machines > I'm responsible for, especially not on machines that have > user accounts or services that are not restricted to jails. > > I also think it is inefficient to let the kernel render > data to ASCII, and then have userland tools parse that > ASCII data again. That's ridiculous. There is no sane > reason for putting kernel data as ASCII text into a pseudo > file system. I don't want to start a debate, but I disagree on the last point. If anything, the filesystem concept for data acquisition (from the kernel) most definitely falls under the "true UNIX way". I disagree with this data being made available under /proc, but I do feel what's provided as a simple file-based interface is the Right Thing(tm). Here's why: Programmers are strictly limited to the sysctl(3) interface, or get to do horrible things like fork()/exec() sysctl(8) repetitively for data. How efficient! Aside from C, I'm not aware of any programming languages that have native tie-ins to sysctl(3). I am explicitly excluding third-party modules for perl and other whatnots; they're silly. With a filesystem that provides sysctl data, you can literally use anything you want to get information: /bin/sh, python, perl, PHP, Tcl/Tk, Ruby, Java, or anything else. As it stands today, the programming language is effectively made retarded by repetitive calls to sysctl(8) to get data, check exit codes, not to mention the repetitive fork()/exec() requirements. For years now I have been considering a sysctl filesystem (e.g. mounted as /sysctl) which would solve this dilemma. Read-only might be a wise choice for this too. But this is beyond my skill set at this time, and the existing documentation/examples for a pseudo filesystem are really not that great. By the way, did you know present-day FreeBSD "ps -e" doesn't work? Try it and notice what the first line of output is. There are some other base system utilities that behave the same way (thing-X doesn't work without procps, and god forbid you use/mount it). I agree that procps should be removed, but the way this came about was obviously done in haste. Not cool. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Mon Feb 21 21:49:44 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9BA3C106566C; Mon, 21 Feb 2011 21:49:44 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by mx1.freebsd.org (Postfix) with ESMTP id E53C58FC08; Mon, 21 Feb 2011 21:49:43 +0000 (UTC) Received: by bwz13 with SMTP id 13so2855513bwz.17 for ; Mon, 21 Feb 2011 13:49:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:subject:references:x-comment-to:date :in-reply-to:message-id:user-agent:mime-version:content-type; bh=6C//JpSJ1BkRkPFDtUTt+Jk4R4PqXv/Z7XoTahBHJkw=; b=exRwoTpmzGdpCyKsTmieKH+8L7jVDJwbbUfoC4uV0SYcuimZbpsMY4FRB6rPDPfw50 g9axQNsbcMZMSbc6M91+hRc2rXtE/pisTgr4DxT36PwfCtMn52T0G5JXudHkP/YyUwPc dU7J/CTcYZtihjIL5znHBWJ9L1l3KAoB2DAQ0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:references:x-comment-to:date:in-reply-to :message-id:user-agent:mime-version:content-type; b=qO6+38OoFGxv8/k6xaDrx4tS2RQdwL5tJd9DC/UDTxMMIOaQFmreq1wkiPVJ0JXT2C fYyH8mBleW7SBGzLzsCjyRXn2qylxJ9fBppJJaY9SBOn/GdGOnLizRoHE1epiw1mmjYB d1bLpxOaSqleyxiJ+qjJja1shF9ztPCtMfiGI= Received: by 10.204.68.65 with SMTP id u1mr1813323bki.193.1298324981809; Mon, 21 Feb 2011 13:49:41 -0800 (PST) Received: from localhost ([95.69.172.154]) by mx.google.com with ESMTPS id x38sm4054089bkj.13.2011.02.21.13.49.39 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 21 Feb 2011 13:49:40 -0800 (PST) From: Mikolaj Golub To: Christian Vogt References: <2C4EE30F-7731-4B84-ADC6-75C0266863F0@haw-hamburg.de> X-Comment-To: Christian Vogt Date: Mon, 21 Feb 2011 23:49:37 +0200 In-Reply-To: <2C4EE30F-7731-4B84-ADC6-75C0266863F0@haw-hamburg.de> (Christian Vogt's message of "Mon, 21 Feb 2011 16:55:35 +0100") Message-ID: <86ei713vny.fsf@kopusha.home.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Cc: freebsd-fs@FreeBSD.org, Pawel Jakub Dawidek Subject: Re: hastd Failover with ucarp 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: Mon, 21 Feb 2011 21:49:44 -0000 --=-=-= On Mon, 21 Feb 2011 16:55:35 +0100 Christian Vogt wrote: CV> Hello! CV> Thanks for the great work, I like this straight-forward FreeBSD a lot CV> from what I experienced untill now. I used the HAST How-To from CV> http://wiki.freebsd.org/HAST and it works perfectly if I use "pkill -USR2 CV> -f 'ucarp -B'" to initiate the failover. The secondary node becomes CV> primary and the carp-interface is switched over to it. CV> But if I do a hard shutdown of the primary node it doesn't work, the CV> secondary node doesn't get primary. The ucarp-up script on the secondary CV> node is executed, but it fails because of the still running secondary CV> worker process (Secondary process for resource test is still running CV> after 30 seconds). Is the secondary process expected to end CV> automatically, when the primary process fails? I think it should exit but currently it does not. In r207371 timeouts for primary incoming and outgoing and secondary outgoing were added but not for secondary incoming. After keep alive mechanism was implemented I think we can add timeout for secondary incoming too. E.g. like in the attached patch? With the patch the secondary will exit in 20 seconds if it does not receive any packets from the primary. Or may by it is better to replace RETRY_SLEEP with timeout configuration parameter, both for keep alive/reconnection interval in primary and secondary incoming timeout? -- Mikolaj Golub --=-=-= Content-Type: text/x-patch Content-Disposition: attachment; filename=hastd.secondary_incoming_timeout.patch Index: sbin/hastd/secondary.c =================================================================== --- sbin/hastd/secondary.c (revision 218930) +++ sbin/hastd/secondary.c (working copy) @@ -416,7 +416,7 @@ hastd_secondary(struct hast_resource *res, struct PJDLOG_VERIFY(sigprocmask(SIG_SETMASK, &mask, NULL) == 0); /* Error in setting timeout is not critical, but why should it fail? */ - if (proto_timeout(res->hr_remotein, 0) < 0) + if (proto_timeout(res->hr_remotein, RETRY_SLEEP * 2) < 0) pjdlog_errno(LOG_WARNING, "Unable to set connection timeout"); if (proto_timeout(res->hr_remoteout, res->hr_timeout) < 0) pjdlog_errno(LOG_WARNING, "Unable to set connection timeout"); Index: sbin/hastd/hast.h =================================================================== --- sbin/hastd/hast.h (revision 218930) +++ sbin/hastd/hast.h (working copy) @@ -97,6 +97,9 @@ #define HAST_ADDRSIZE 1024 #define HAST_TOKEN_SIZE 16 +/* Number of seconds to sleep between reconnect retries or keepalive packets. */ +#define RETRY_SLEEP 10 + struct hastd_config { /* Address to communicate with hastctl(8). */ char hc_controladdr[HAST_ADDRSIZE]; Index: sbin/hastd/primary.c =================================================================== --- sbin/hastd/primary.c (revision 218930) +++ sbin/hastd/primary.c (working copy) @@ -150,10 +150,6 @@ static pthread_mutex_t metadata_lock; * and remote components. */ #define HAST_NCOMPONENTS 2 -/* - * Number of seconds to sleep between reconnect retries or keepalive packets. - */ -#define RETRY_SLEEP 10 #define ISCONNECTED(res, no) \ ((res)->hr_remotein != NULL && (res)->hr_remoteout != NULL) --=-=-=-- From owner-freebsd-fs@FreeBSD.ORG Tue Feb 22 03:27:25 2011 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A03AB106566C; Tue, 22 Feb 2011 03:27:25 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 74C908FC13; Tue, 22 Feb 2011 03:27:25 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1M3RPtl026142; Tue, 22 Feb 2011 03:27:25 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1M3RPtH026138; Tue, 22 Feb 2011 03:27:25 GMT (envelope-from linimon) Date: Tue, 22 Feb 2011 03:27:25 GMT Message-Id: <201102220327.p1M3RPtH026138@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/154930: [zfs] cannot delete/unlink file from full volume -> ENOSPC 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, 22 Feb 2011 03:27:25 -0000 Old Synopsis: ZFS: cannot delete/unlink file from full volume -> ENOSPC New Synopsis: [zfs] cannot delete/unlink file from full volume -> ENOSPC Responsible-Changed-From-To: freebsd-ports-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Tue Feb 22 03:26:44 UTC 2011 Responsible-Changed-Why: Does not appear to be a ports PR. Reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=154930 From owner-freebsd-fs@FreeBSD.ORG Tue Feb 22 08:59:16 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 98CFF106566B for ; Tue, 22 Feb 2011 08:59:16 +0000 (UTC) (envelope-from kellydeanch@yahoo.com) Received: from nm26.bullet.mail.ac4.yahoo.com (nm26.bullet.mail.ac4.yahoo.com [98.139.52.223]) by mx1.freebsd.org (Postfix) with SMTP id 2032A8FC15 for ; Tue, 22 Feb 2011 08:59:15 +0000 (UTC) Received: from [98.139.52.190] by nm26.bullet.mail.ac4.yahoo.com with NNFMP; 22 Feb 2011 08:45:37 -0000 Received: from [98.139.52.153] by tm3.bullet.mail.ac4.yahoo.com with NNFMP; 22 Feb 2011 08:45:37 -0000 Received: from [127.0.0.1] by omp1036.mail.ac4.yahoo.com with NNFMP; 22 Feb 2011 08:45:37 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 12208.83416.bm@omp1036.mail.ac4.yahoo.com Received: (qmail 58547 invoked by uid 60001); 22 Feb 2011 08:45:36 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1298364336; bh=7s1amI0p4AigdhJ3DrwV9mReJNHAAP/Sd+lNyb9rWqM=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=f2ZyINmcXwESpVIY/1eSEyiNcDqE0lUk3CL4nZzrWZwb+3GJdDyq5GvIiW8xErsUOMfj7p2zViIKY4hI/yKcD8QN7R2wThjcgxA0icTIv9oiJe8gBOEhpDJPr5B6rZ+lC7+nVmBu6ixqw2fTSniLCAGM0mhag/GIlUrQZci5T6I= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=FO+8NmI++gOHMxsRTHreVPH35HMdMMDbjerU36TDuFzGRei6XvGVrUitj1c2q35pueB4SiSBoawMfbeYodkNFVpmw5GwrdajwbN15AnUsz+yIqyPraESIHDXimgsJr3zLq3pjmAKY88fRGugtF7xU1Xzi8sOHl7+VAs2Igw/1W4=; Message-ID: <476667.58379.qm@web121516.mail.ne1.yahoo.com> X-YMail-OSG: Y2AaFAQVM1m4GQDYLB4gsaAvLZIMBvv9lLnXaa08hSwvbpi lUDiG.iY8vS6WJtOU1ycXktlpt7EMcXhT6qcv7fQx9Oph02pfTsmsC9.Zhdf FqNF0LZlcV7h939xIcn6rKzxIMhyhQyd.02SmQuohh8sqhwoKn_vSzwzf4YE 0p7vyvIX5EDT6W3eDjG6MO4qyu__CJYZMW.wq8Q-- Received: from [192.251.226.205] by web121516.mail.ne1.yahoo.com via HTTP; Tue, 22 Feb 2011 00:45:36 PST X-Mailer: YahooMailClassic/11.4.20 YahooMailWebService/0.8.109.292656 Date: Tue, 22 Feb 2011 00:45:36 -0800 (PST) From: Kelly Dean To: freebsd-fs@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Subject: Re: Why is procfs deprecated in favor of procstat? 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, 22 Feb 2011 08:59:16 -0000 I see five different issues, so I need to clarify which one I was asking about. 1. How to request the data in question from the kernel: by reading a file, or by making a dedicated system call. Jeremy says read a file. 2. The format the kernel returns the data in. Oliver says the Plan 9 way of the kernel rendering text and then userland tools parsing text is silly. The kernel should return binary, which userland tools can then use directly, or render to text for a person to read. 3. Conflating /proc with Jeremy's /sysctl. 4. Whether /proc and/or /sysctl should be read-only. 5. Whether things in different security domains should see the same procfs. The question I meant to ask was just the first one. What's wrong with requesting the data by reading a file instead of making a dedicated system call? What's the advantage of the system call? But since the other issues came up: 2, I agree the kernel should return binary. 3, separate /proc and /sysctl. 4, no comment. 5, Oliver, didn't you answer your own objection? If things are supposed to be in the same security domain, then there can't be a vulnerability caused by them sharing a common procfs, and if they're supposed to be in different security domains, then put them in jails, where they don't share a common procfs. Jeremy, when you said procfs should be removed, did you mean just for the same reasons Oliver said, or did you have other reasons? From owner-freebsd-fs@FreeBSD.ORG Tue Feb 22 09:52:14 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9EB61106566C for ; Tue, 22 Feb 2011 09:52:14 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta11.emeryville.ca.mail.comcast.net (qmta11.emeryville.ca.mail.comcast.net [76.96.27.211]) by mx1.freebsd.org (Postfix) with ESMTP id 7F8C08FC18 for ; Tue, 22 Feb 2011 09:52:13 +0000 (UTC) Received: from omta21.emeryville.ca.mail.comcast.net ([76.96.30.88]) by qmta11.emeryville.ca.mail.comcast.net with comcast id Axra1g0021u4NiLABxsD1K; Tue, 22 Feb 2011 09:52:13 +0000 Received: from koitsu.dyndns.org ([98.248.33.18]) by omta21.emeryville.ca.mail.comcast.net with comcast id AxsB1g0020PUQVN8hxsCKA; Tue, 22 Feb 2011 09:52:12 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id B2EA79B422; Tue, 22 Feb 2011 01:52:11 -0800 (PST) Date: Tue, 22 Feb 2011 01:52:11 -0800 From: Jeremy Chadwick To: Kelly Dean Message-ID: <20110222095211.GA96223@icarus.home.lan> References: <201102211707.p1LH7c8n075660@lurza.secnetix.de> <476667.58379.qm@web121516.mail.ne1.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <476667.58379.qm@web121516.mail.ne1.yahoo.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@FreeBSD.ORG Subject: Re: Why is procfs deprecated in favor of procstat? 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, 22 Feb 2011 09:52:14 -0000 On Tue, Feb 22, 2011 at 12:45:36AM -0800, Kelly Dean wrote: > [ snipping stuff that I have no real response to :-) ] > > Jeremy, when you said procfs should be removed, did you mean just for > the same reasons Oliver said, or did you have other reasons? The security issues are long-standing and there have been many over the years, but the real reason is something that's less evident (or at least less directly apparent): Simply put, procfs on FreeBSD has been neglected. There isn't a lot of attention being given to it, and the only modifications in recent months/years have been generally minor compared to the rest of the tree. You can review some of the commits yourself: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/fs/procfs/ Others like yourself have asked what the state of procfs is, going back as far as 2005. Be sure to read the reply as well: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/questions/2005-05/2607.html There was also a commit comment circa 2008 to the RELENG_7 branch that indicates procfs is "now-deprecated": http://freshbsd.org/2008/04/10/20/54/02 ...yet there have been commits as recent as 2009 to fix important utilities -- gcore(1) and gdb(1) -- to work without procps, which adds further evidence that procfs may have been hastily forgotten/dropped without a full review of what relied upon it: http://freshbsd.org/2009/12/19/19/30/27 Alternate solutions or changes to procfs have been mentioned over the years, such as in 2008 by a user on freebsd-arch, who received no reply: http://lists.freebsd.org/pipermail/freebsd-arch/2008-March/007750.html Finally, there is an official maintainer of procfs (see procfs.c at the first link, then look for the Sep 23 2009 commit). You may want to privately ask that individual what the current state of affairs is. The /sysctl filesystem idea I've had I still feel is the best solution, but *should not* be based on the procfs code (they're two different beasts, despite having similar functionality). It should be written from scratch. I was quite serious when I said I wish I could write such a thing, because the benefits of such are huge, especially when it comes to *any* form of counter/statistic-gathering or monitoring capability on FreeBSD. Honestly, it's a project that seems perfect for GSoC. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Tue Feb 22 13:29:58 2011 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29D4D10656A6 for ; Tue, 22 Feb 2011 13:29:58 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id 9F9EB8FC0C for ; Tue, 22 Feb 2011 13:29:57 +0000 (UTC) Received: from park.js.berklix.net (p5B22F881.dip.t-dialin.net [91.34.248.129]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id p1MD4bDP085886 for ; Tue, 22 Feb 2011 13:04:38 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by park.js.berklix.net (8.13.8/8.13.8) with ESMTP id p1MD4ZB8091406 for ; Tue, 22 Feb 2011 14:04:35 +0100 (CET) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.3/8.14.3) with ESMTP id p1MD4TlH040942 for ; Tue, 22 Feb 2011 14:04:35 +0100 (CET) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201102221304.p1MD4TlH040942@fire.js.berklix.net> To: fs@freebsd.org From: "Julian H. Stacey" Organization: http://www.berklix.com BSD Linux Unix Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com/~jhs/cv/ Date: Tue, 22 Feb 2011 14:04:29 +0100 Sender: jhs@berklix.com Cc: Subject: Flash drives dangerously hard to purge of sensitive data 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, 22 Feb 2011 13:29:58 -0000 fs@freebsd.org Usenix Conference Fast11 15-17 Feb 2011 http://www.usenix.org/events/fast11/tech/ Paper: (15 pages) http://www.usenix.org/events/fast11/tech/full_papers/Wei.pdf Review: http://www.theregister.co.uk/2011/02/21/flash_drive_erasing_peril/ "Flash drives dangerously hard to purge of sensitive data - When secure wiping isn't" Ive only read the review so far, but covers topics re file system access & file deletion. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below indented '> ' original, to read like a play script, in order. Mail plain text format; Not quoted-printable, Not HTML, Not base 64. From owner-freebsd-fs@FreeBSD.ORG Tue Feb 22 13:37:46 2011 Return-Path: Delivered-To: fs@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id D45EF1065696; Tue, 22 Feb 2011 13:37:46 +0000 (UTC) Date: Tue, 22 Feb 2011 13:37:46 +0000 From: Alexander Best To: "Julian H. Stacey" Message-ID: <20110222133746.GA95981@freebsd.org> References: <201102221304.p1MD4TlH040942@fire.js.berklix.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201102221304.p1MD4TlH040942@fire.js.berklix.net> Cc: fs@freebsd.org Subject: Re: Flash drives dangerously hard to purge of sensitive data 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, 22 Feb 2011 13:37:46 -0000 On Tue Feb 22 11, Julian H. Stacey wrote: > fs@freebsd.org > Usenix Conference Fast11 15-17 Feb 2011 > http://www.usenix.org/events/fast11/tech/ > Paper: (15 pages) > http://www.usenix.org/events/fast11/tech/full_papers/Wei.pdf > Review: > http://www.theregister.co.uk/2011/02/21/flash_drive_erasing_peril/ > "Flash drives dangerously hard to purge of sensitive data > - When secure wiping isn't" > Ive only read the review so far, but covers topics re file system > access & file deletion. i think this is one of the issues that caused a rather long and techy discussion on svn-src-head et al. regarding rm(1)'s -P switch. cheers. alex > > Cheers, > Julian > -- > Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com > Reply below indented '> ' original, to read like a play script, in order. > Mail plain text format; Not quoted-printable, Not HTML, Not base 64. > -- a13x From owner-freebsd-fs@FreeBSD.ORG Tue Feb 22 14:40:13 2011 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E51721065670 for ; Tue, 22 Feb 2011 14:40:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D40578FC2C for ; Tue, 22 Feb 2011 14:40:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1MEeDDD080513 for ; Tue, 22 Feb 2011 14:40:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1MEeDQh080512; Tue, 22 Feb 2011 14:40:13 GMT (envelope-from gnats) Date: Tue, 22 Feb 2011 14:40:13 GMT Message-Id: <201102221440.p1MEeDQh080512@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Martin Matuska Cc: Subject: Re: kern/154930: [zfs] cannot delete/unlink file from full volume -> ENOSPC X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Martin Matuska List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Feb 2011 14:40:14 -0000 The following reply was made to PR kern/154930; it has been noted by GNATS. From: Martin Matuska To: bug-followup@FreeBSD.org, mandree@FreeBSD.org Cc: Subject: Re: kern/154930: [zfs] cannot delete/unlink file from full volume -> ENOSPC Date: Tue, 22 Feb 2011 15:30:34 +0100 I was unable to reproduce your problem. But I was able to reproduce a different situation: - on a dataset with one or more snapshots I am unable to delete files (ENOSPC) if the dataset got full. If this is your case, then: - deleting files does not unlink them from the snapshot. - you must first delete a specific snapshot (or all snapshots linking the file) to free space. Cheers, mm From owner-freebsd-fs@FreeBSD.ORG Tue Feb 22 15:50:09 2011 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1634106566B for ; Tue, 22 Feb 2011 15:50:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 803218FC17 for ; Tue, 22 Feb 2011 15:50:09 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1MFo9dO054162 for ; Tue, 22 Feb 2011 15:50:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1MFo9Ld054161; Tue, 22 Feb 2011 15:50:09 GMT (envelope-from gnats) Date: Tue, 22 Feb 2011 15:50:09 GMT Message-Id: <201102221550.p1MFo9Ld054161@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Matthias Andree Cc: Subject: Re: kern/154930: [zfs] cannot delete/unlink file from full volume -> ENOSPC X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Andree List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Feb 2011 15:50:09 -0000 The following reply was made to PR kern/154930; it has been noted by GNATS. From: Matthias Andree To: Martin Matuska Cc: bug-followup@FreeBSD.org Subject: Re: kern/154930: [zfs] cannot delete/unlink file from full volume -> ENOSPC Date: Tue, 22 Feb 2011 16:06:47 +0100 Am 22.02.2011 15:30, schrieb Martin Matuska: > I was unable to reproduce your problem. > > But I was able to reproduce a different situation: > - on a dataset with one or more snapshots I am unable to delete files > (ENOSPC) if the dataset got full. > > If this is your case, then: > - deleting files does not unlink them from the snapshot. > - you must first delete a specific snapshot (or all snapshots linking > the file) to free space. Hi Martin, no snapshots were ever used on the zpools or zfs volumes -- I had checked that previously. Only truncation of a 20 M file would allow me to delete files. Best regards Matthias -- Matthias Andree ports committer From owner-freebsd-fs@FreeBSD.ORG Tue Feb 22 16:19:57 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B7CD21065673 for ; Tue, 22 Feb 2011 16:19:57 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 87A968FC14 for ; Tue, 22 Feb 2011 16:19:57 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 3ADD246B23; Tue, 22 Feb 2011 11:19:57 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.10]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 7802C8A01D; Tue, 22 Feb 2011 11:19:56 -0500 (EST) From: John Baldwin To: freebsd-fs@freebsd.org Date: Tue, 22 Feb 2011 09:31:17 -0500 User-Agent: KMail/1.13.5 (FreeBSD/7.4-CBSD-20110107; KDE/4.4.5; amd64; ; ) References: <201102211707.p1LH7c8n075660@lurza.secnetix.de> <476667.58379.qm@web121516.mail.ne1.yahoo.com> <20110222095211.GA96223@icarus.home.lan> In-Reply-To: <20110222095211.GA96223@icarus.home.lan> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201102220931.17733.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Tue, 22 Feb 2011 11:19:56 -0500 (EST) X-Virus-Scanned: clamav-milter 0.96.3 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=0.5 required=4.2 tests=BAYES_00,MAY_BE_FORGED, RDNS_DYNAMIC autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on bigwig.baldwin.cx Cc: Kelly Dean Subject: Re: Why is procfs deprecated in favor of procstat? 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, 22 Feb 2011 16:19:57 -0000 On Tuesday, February 22, 2011 4:52:11 am Jeremy Chadwick wrote: > On Tue, Feb 22, 2011 at 12:45:36AM -0800, Kelly Dean wrote: > > [ snipping stuff that I have no real response to :-) ] > > > > Jeremy, when you said procfs should be removed, did you mean just for > > the same reasons Oliver said, or did you have other reasons? > > The security issues are long-standing and there have been many over the > years, but the real reason is something that's less evident (or at least > less directly apparent): Actually, the replacement for procfs is not sysctl, but ptrace(2), and there has been a long-running process in place to migrate tools such as truss, etc. from using procfs to use ptrace(2) instead and to add new features to ptrace(2) when there were things it did not support that procfs did. One could argue that some of the more recent things like the sysctl's for procstat -v or procstat -k should have been implemented as new ptrace OPs rather than sysctls (and I'd probably agree with you). -- John Baldwin From owner-freebsd-fs@FreeBSD.ORG Tue Feb 22 19:22:05 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF9801065670; Tue, 22 Feb 2011 19:22:05 +0000 (UTC) (envelope-from bfriesen@simple.dallas.tx.us) Received: from blade.simplesystems.org (blade.simplesystems.org [65.66.246.74]) by mx1.freebsd.org (Postfix) with ESMTP id 6F2B18FC12; Tue, 22 Feb 2011 19:22:05 +0000 (UTC) Received: from freddy.simplesystems.org (freddy.simplesystems.org [65.66.246.65]) by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id p1MJAv6s006999; Tue, 22 Feb 2011 13:10:57 -0600 (CST) Date: Tue, 22 Feb 2011 13:10:57 -0600 (CST) From: Bob Friesenhahn X-X-Sender: bfriesen@freddy.simplesystems.org To: John Baldwin In-Reply-To: <201102220931.17733.jhb@freebsd.org> Message-ID: References: <201102211707.p1LH7c8n075660@lurza.secnetix.de> <476667.58379.qm@web121516.mail.ne1.yahoo.com> <20110222095211.GA96223@icarus.home.lan> <201102220931.17733.jhb@freebsd.org> User-Agent: Alpine 2.01 (GSO 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (blade.simplesystems.org [65.66.246.90]); Tue, 22 Feb 2011 13:10:57 -0600 (CST) Cc: freebsd-fs@freebsd.org, Kelly Dean Subject: Re: Why is procfs deprecated in favor of procstat? 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, 22 Feb 2011 19:22:06 -0000 On Tue, 22 Feb 2011, John Baldwin wrote: > > Actually, the replacement for procfs is not sysctl, but ptrace(2), and there I have been following this discussion with my jaw agape. It seems that the many men standing around this elephant are all perceiving completely different things based on their own interests and experiences. My own software is using procfs to efficiently determine the path to the currently running executable. I am sure that other software does the same since Linux procfs (and probably OS X) supports the same mechanism. It is difficult to imagine how this would be done via ptrace(2). Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ From owner-freebsd-fs@FreeBSD.ORG Tue Feb 22 20:50:16 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31D161065673 for ; Tue, 22 Feb 2011 20:50:16 +0000 (UTC) (envelope-from prvs=0279125ef=Christian.Vogt@haw-hamburg.de) Received: from mx3.haw-public.haw-hamburg.de (mx3.haw-public.haw-hamburg.de [141.22.6.2]) by mx1.freebsd.org (Postfix) with ESMTP id B405C8FC0A for ; Tue, 22 Feb 2011 20:50:15 +0000 (UTC) Received: from dehawshub01.mailcluster.haw-hamburg.de ([141.22.200.36]) by mail3.is.haw-hamburg.de with ESMTP/TLS/RC4-MD5; 22 Feb 2011 21:40:06 +0100 Received: from dehawscas02.mailcluster.haw-hamburg.de (141.22.200.34) by DEHAWSHUB01.mailcluster.haw-hamburg.de (141.22.200.36) with Microsoft SMTP Server (TLS) id 8.1.358.0; Tue, 22 Feb 2011 21:40:06 +0100 Received: from [172.20.0.20] (141.22.200.51) by haw-mailer.haw-hamburg.de (141.22.200.80) with Microsoft SMTP Server (TLS) id 8.1.358.0; Tue, 22 Feb 2011 21:40:06 +0100 MIME-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset="us-ascii" From: Christian Vogt In-Reply-To: <86ei713vny.fsf@kopusha.home.net> Date: Tue, 22 Feb 2011 21:40:05 +0100 Content-Transfer-Encoding: quoted-printable Message-ID: <8B15C618-4560-4ABE-BD8E-94872A33F5F6@haw-hamburg.de> References: <2C4EE30F-7731-4B84-ADC6-75C0266863F0@haw-hamburg.de> <86ei713vny.fsf@kopusha.home.net> To: Mikolaj Golub X-Mailer: Apple Mail (2.1082) Cc: freebsd-fs@FreeBSD.org Subject: Re: hastd Failover with ucarp 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, 22 Feb 2011 20:50:16 -0000 >=20 > On Mon, 21 Feb 2011 16:55:35 +0100 Christian Vogt wrote: >=20 > CV> Hello!=20 >=20 > CV> Thanks for the great work, I like this straight-forward FreeBSD a = lot > CV> from what I experienced untill now. I used the HAST How-To from > CV> http://wiki.freebsd.org/HAST and it works perfectly if I use = "pkill -USR2 > CV> -f 'ucarp -B'" to initiate the failover. The secondary node = becomes > CV> primary and the carp-interface is switched over to it. >=20 > CV> But if I do a hard shutdown of the primary node it doesn't work, = the > CV> secondary node doesn't get primary. The ucarp-up script on the = secondary > CV> node is executed, but it fails because of the still running = secondary > CV> worker process (Secondary process for resource test is still = running > CV> after 30 seconds). Is the secondary process expected to end > CV> automatically, when the primary process fails? >=20 > I think it should exit but currently it does not. In r207371 timeouts = for > primary incoming and outgoing and secondary outgoing were added but = not for > secondary incoming. After keep alive mechanism was implemented I think = we can > add timeout for secondary incoming too. E.g. like in the attached = patch? >=20 > With the patch the secondary will exit in 20 seconds if it does not = receive > any packets from the primary. >=20 > Or may by it is better to replace RETRY_SLEEP with timeout = configuration > parameter, both for keep alive/reconnection interval in primary and = secondary > incoming timeout? >=20 > --=20 > Mikolaj Golub >=20 > Thanks for your help, this solved the issue! I'm still going to use the = carp+devd variant as proposed by Freddie, but this seems to be a good = failover if carp doesn't work properly. Christian Vogt= From owner-freebsd-fs@FreeBSD.ORG Tue Feb 22 21:14:50 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A5BE106566B; Tue, 22 Feb 2011 21:14:50 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 772FE8FC18; Tue, 22 Feb 2011 21:14:48 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id p1MLEi4x031910 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 Feb 2011 23:14:44 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p1MLEiqx062487; Tue, 22 Feb 2011 23:14:44 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p1MLEiAK062486; Tue, 22 Feb 2011 23:14:44 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 22 Feb 2011 23:14:44 +0200 From: Kostik Belousov To: Bob Friesenhahn Message-ID: <20110222211444.GD78089@deviant.kiev.zoral.com.ua> References: <201102211707.p1LH7c8n075660@lurza.secnetix.de> <476667.58379.qm@web121516.mail.ne1.yahoo.com> <20110222095211.GA96223@icarus.home.lan> <201102220931.17733.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="hHivBRp+DJn3Iiyu" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-fs@freebsd.org, Kelly Dean Subject: Re: Why is procfs deprecated in favor of procstat? 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, 22 Feb 2011 21:14:50 -0000 --hHivBRp+DJn3Iiyu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 22, 2011 at 01:10:57PM -0600, Bob Friesenhahn wrote: > On Tue, 22 Feb 2011, John Baldwin wrote: > > > >Actually, the replacement for procfs is not sysctl, but ptrace(2), and= =20 > >there >=20 > I have been following this discussion with my jaw agape. It seems=20 > that the many men standing around this elephant are all perceiving=20 > completely different things based on their own interests and=20 > experiences. >=20 > My own software is using procfs to efficiently determine the path to=20 > the currently running executable. I am sure that other software does=20 > the same since Linux procfs (and probably OS X) supports the same=20 > mechanism. It is difficult to imagine how this would be done via=20 > ptrace(2). Look at the PT_VM_TIMESTAMP + PT_VM_ENTRY. You would iterate over the the mappings in the address space and look at the binaries at pve_path, if any. The one that is elf object f the ET_EXEC type is the binary. It is somewhat clumsy but the end result is the same as if reading /proc//file. Or, you use sysctl kern.proc.vmmap and get essentially the same data. PT_VM_ENTRY was added long after the sysctl, I did not objected exactly because ptrace(2) looked more logical. The advantage of using procfs or sysctl instead of ptrace(2) is that you do not need to attach as debugger, causing the issues with signal delivery for the debugee. --hHivBRp+DJn3Iiyu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk1kJ0MACgkQC3+MBN1Mb4iqWACeKYKK7dE1WNqDs4lcG0Hubgvw V3MAn3gzso/6qkl9y/NMUOUrtWD402aX =b/TU -----END PGP SIGNATURE----- --hHivBRp+DJn3Iiyu-- From owner-freebsd-fs@FreeBSD.ORG Tue Feb 22 21:26:05 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04C8A1065672; Tue, 22 Feb 2011 21:26:05 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 7003B8FC08; Tue, 22 Feb 2011 21:26:04 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id p1MLQ0Pl032615 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 Feb 2011 23:26:01 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p1MLQ0AI062605; Tue, 22 Feb 2011 23:26:00 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p1MLQ0QR062604; Tue, 22 Feb 2011 23:26:00 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 22 Feb 2011 23:26:00 +0200 From: Kostik Belousov To: Ben Kaduk Message-ID: <20110222212600.GG78089@deviant.kiev.zoral.com.ua> References: <201102221738.p1MHchsd016185@svn.freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Hl7iIDUZZE9gOHs4" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-fs@freebsd.org, FreeBSD-Hackers , Bruce Cran Subject: Re: svn commit: r218953 - stable/8/usr.sbin/sysinstall 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, 22 Feb 2011 21:26:05 -0000 --Hl7iIDUZZE9gOHs4 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 22, 2011 at 01:06:38PM -0500, Ben Kaduk wrote: > [replying to the MFC that triggered the connection] >=20 > On Tue, Feb 22, 2011 at 12:38 PM, Bruce Cran wrote: > > Author: brucec > > Date: Tue Feb 22 17:38:43 2011 > > New Revision: 218953 > > URL: http://svn.freebsd.org/changeset/base/218953 > > > > Log: > > =9AMFC r218840: > > > > =9ARemove the quotas option from the Startup Services menu. > > =9AGENERIC has no support for quotas so this option has no effect. >=20 > Do you know why GENERIC does not have quota support enabled? I note > that the Debian/kFreeBSD folk have enabled quota support for the > kernel they ship: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D608995 >=20 > In that report, emaste@ is quoted as saying: > > If you mean "kFreeBSD should ship with a quota-enabled kernel" then I'd > > say go for it. The reason we don't have it on in upstream FreeBSD is > > largely historical; enabling quotas used to require additional locking > > that caused performance and other issues. The additional locking is now > > not required, and it's just that nobody has stepped in to turn them on. >=20 > If you believe everything you read on the internet, "In order to > achieve a modern operating system, the quota support should be active > by default, not achieved only after compilation of a custom kernel." >=20 > Is there more to "stepping in and turning them on" than just the > one-line change? I promise to enable UFS quotas in GENERIC in one week unless anybody objects now. --Hl7iIDUZZE9gOHs4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk1kKegACgkQC3+MBN1Mb4gfpQCgjMiTff37Oxv/J4wC2o+XuZpw 0ycAoJTefNzu36dpTF7y2dfZshQjnb0A =Z80l -----END PGP SIGNATURE----- --Hl7iIDUZZE9gOHs4-- From owner-freebsd-fs@FreeBSD.ORG Wed Feb 23 08:58:23 2011 Return-Path: Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 989541065697 for ; Wed, 23 Feb 2011 08:58:23 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.garage.freebsd.pl (60.wheelsystems.com [83.12.187.60]) by mx1.freebsd.org (Postfix) with ESMTP id 453D08FC19 for ; Wed, 23 Feb 2011 08:58:22 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 71DA145CAC; Wed, 23 Feb 2011 09:58:20 +0100 (CET) Received: from localhost (58.wheelsystems.com [83.12.187.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id B5C8C4569A; Wed, 23 Feb 2011 09:58:14 +0100 (CET) Date: Wed, 23 Feb 2011 09:57:56 +0100 From: Pawel Jakub Dawidek To: Jeremy Chadwick Message-ID: <20110223085755.GA1749@garage.freebsd.pl> References: <457880.36028.qm@web121501.mail.ne1.yahoo.com> <201102211707.p1LH7c8n075660@lurza.secnetix.de> <20110221174100.GA77744@icarus.home.lan> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jRHKVT23PllUwdXP" Content-Disposition: inline In-Reply-To: <20110221174100.GA77744@icarus.home.lan> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 9.0-CURRENT amd64 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-3.9 required=4.5 tests=ALL_TRUSTED,BAYES_00, RCVD_IN_SORBS_DUL autolearn=ham version=3.0.4 Cc: freebsd-fs@FreeBSD.ORG, kellydeanch@yahoo.com Subject: Re: Why is procfs deprecated in favor of procstat? 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, 23 Feb 2011 08:58:23 -0000 --jRHKVT23PllUwdXP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 21, 2011 at 09:41:00AM -0800, Jeremy Chadwick wrote: > For years now I have been considering a sysctl filesystem (e.g. mounted > as /sysctl) which would solve this dilemma. Read-only might be a wise > choice for this too. But this is beyond my skill set at this time, and > the existing documentation/examples for a pseudo filesystem are really > not that great. http://www.mail-archive.com/freebsd-hackers@freebsd.org/msg38829.html :) --=20 Pawel Jakub Dawidek http://www.wheelsystems.com pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --jRHKVT23PllUwdXP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk1kzBMACgkQForvXbEpPzRD/ACgtosebYGuPGiWDdFqC2pphTxH Ef0AoPnH3OF1elqdDMgWYWoZGfyZvsFc =AfkQ -----END PGP SIGNATURE----- --jRHKVT23PllUwdXP-- From owner-freebsd-fs@FreeBSD.ORG Wed Feb 23 09:31:46 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 730D2106566B for ; Wed, 23 Feb 2011 09:31:46 +0000 (UTC) (envelope-from ml@my.gd) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 36E0E8FC08 for ; Wed, 23 Feb 2011 09:31:44 +0000 (UTC) Received: by ywf9 with SMTP id 9so1069396ywf.13 for ; Wed, 23 Feb 2011 01:31:44 -0800 (PST) Received: by 10.90.100.8 with SMTP id x8mr4952623agb.53.1298453504057; Wed, 23 Feb 2011 01:31:44 -0800 (PST) Received: from dfleuriot-at-hi-media.com ([83.167.62.196]) by mx.google.com with ESMTPS id 17sm1574793anx.13.2011.02.23.01.31.42 (version=SSLv3 cipher=OTHER); Wed, 23 Feb 2011 01:31:43 -0800 (PST) Message-ID: <4D64D3FD.5000301@my.gd> Date: Wed, 23 Feb 2011 10:31:41 +0100 From: Damien Fleuriot User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <457880.36028.qm@web121501.mail.ne1.yahoo.com> <201102211707.p1LH7c8n075660@lurza.secnetix.de> <20110221174100.GA77744@icarus.home.lan> <20110223085755.GA1749@garage.freebsd.pl> In-Reply-To: <20110223085755.GA1749@garage.freebsd.pl> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: Why is procfs deprecated in favor of procstat? 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, 23 Feb 2011 09:31:46 -0000 On 2/23/11 9:57 AM, Pawel Jakub Dawidek wrote: > On Mon, Feb 21, 2011 at 09:41:00AM -0800, Jeremy Chadwick wrote: >> For years now I have been considering a sysctl filesystem (e.g. mounted >> as /sysctl) which would solve this dilemma. Read-only might be a wise >> choice for this too. But this is beyond my skill set at this time, and >> the existing documentation/examples for a pseudo filesystem are really >> not that great. > > http://www.mail-archive.com/freebsd-hackers@freebsd.org/msg38829.html > > :) > Yummy :) Find below the make output on 8.2-PRERELEASE 21/02/2011 I suppose a lot of stuff changed since 2002 and an update would be required. -- mybsd root /tmp/sysctlfs/sysctlfs # make "/usr/share/mk/bsd.compat.mk", line 35: warning: NOMAN is deprecated in favour of NO_MAN Warning: Object directory not changed from original /tmp/sysctlfs/sysctlfs @ -> /usr/src/sys machine -> /usr/src/sys/amd64/include awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -p awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -q awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -h cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c sysctlfs_subr.c In file included from sysctlfs_subr.c:16: vnode.h:46:26: error: machine/lock.h: No such file or directory In file included from sysctlfs_subr.c:16: vnode.h:118: error: field 'v_interlock' has incomplete type vnode.h:127: error: field 'vpi_lock' has incomplete type vnode.h:128: error: field 'vpi_selinfo' has incomplete type vnode.h:183: error: expected specifier-qualifier-list before 'udev_t' In file included from vnode_if.h:10, from vnode.h:532, from sysctlfs_subr.c:16: vnode_if_newproto.h:11: error: expected specifier-qualifier-list before 'vop_bypass_t' cc1: warnings being treated as errors In file included from vnode.h:532, from sysctlfs_subr.c:16: vnode_if.h: In function 'VOP_ISLOCKED': vnode_if.h:28: warning: passing argument 1 of 'VOP_ISLOCKED_APV' from incompatible pointer type vnode_if.h: In function 'VOP_LOOKUP': vnode_if.h:54: warning: passing argument 1 of 'VOP_LOOKUP_APV' from incompatible pointer type vnode_if.h: In function 'VOP_CACHEDLOOKUP': vnode_if.h:80: warning: passing argument 1 of 'VOP_CACHEDLOOKUP_APV' from incompatible pointer type vnode_if.h: In function 'VOP_CREATE': vnode_if.h:109: warning: passing argument 1 of 'VOP_CREATE_APV' from incompatible pointer type vnode_if.h: In function 'VOP_WHITEOUT': vnode_if.h:135: warning: passing argument 1 of 'VOP_WHITEOUT_APV' from incompatible pointer type vnode_if.h: In function 'VOP_MKNOD': vnode_if.h:164: warning: passing argument 1 of 'VOP_MKNOD_APV' from incompatible pointer type vnode_if.h: In function 'VOP_OPEN': vnode_if.h:196: warning: passing argument 1 of 'VOP_OPEN_APV' from incompatible pointer type vnode_if.h: In function 'VOP_CLOSE': vnode_if.h:225: warning: passing argument 1 of 'VOP_CLOSE_APV' from incompatible pointer type vnode_if.h: In function 'VOP_ACCESS': vnode_if.h:254: warning: passing argument 1 of 'VOP_ACCESS_APV' from incompatible pointer type vnode_if.h: In function 'VOP_ACCESSX': vnode_if.h:283: warning: passing argument 1 of 'VOP_ACCESSX_APV' from incompatible pointer type vnode_if.h: In function 'VOP_GETATTR': vnode_if.h:309: warning: passing argument 1 of 'VOP_GETATTR_APV' from incompatible pointer type vnode_if.h: In function 'VOP_SETATTR': vnode_if.h:335: warning: passing argument 1 of 'VOP_SETATTR_APV' from incompatible pointer type vnode_if.h: In function 'VOP_MARKATIME': vnode_if.h:355: warning: passing argument 1 of 'VOP_MARKATIME_APV' from incompatible pointer type vnode_if.h: In function 'VOP_READ': vnode_if.h:384: warning: passing argument 1 of 'VOP_READ_APV' from incompatible pointer type vnode_if.h: In function 'VOP_WRITE': vnode_if.h:413: warning: passing argument 1 of 'VOP_WRITE_APV' from incompatible pointer type vnode_if.h: In function 'VOP_IOCTL': vnode_if.h:448: warning: passing argument 1 of 'VOP_IOCTL_APV' from incompatible pointer type vnode_if.h: In function 'VOP_POLL': vnode_if.h:477: warning: passing argument 1 of 'VOP_POLL_APV' from incompatible pointer type vnode_if.h: In function 'VOP_KQFILTER': vnode_if.h:500: warning: passing argument 1 of 'VOP_KQFILTER_APV' from incompatible pointer type vnode_if.h: In function 'VOP_REVOKE': vnode_if.h:523: warning: passing argument 1 of 'VOP_REVOKE_APV' from incompatible pointer type vnode_if.h: In function 'VOP_FSYNC': vnode_if.h:549: warning: passing argument 1 of 'VOP_FSYNC_APV' from incompatible pointer type vnode_if.h: In function 'VOP_REMOVE': vnode_if.h:575: warning: passing argument 1 of 'VOP_REMOVE_APV' from incompatible pointer type vnode_if.h: In function 'VOP_LINK': vnode_if.h:601: warning: passing argument 1 of 'VOP_LINK_APV' from incompatible pointer type vnode_if.h: In function 'VOP_RENAME': vnode_if.h:636: warning: passing argument 1 of 'VOP_RENAME_APV' from incompatible pointer type vnode_if.h: In function 'VOP_MKDIR': vnode_if.h:665: warning: passing argument 1 of 'VOP_MKDIR_APV' from incompatible pointer type vnode_if.h: In function 'VOP_RMDIR': vnode_if.h:691: warning: passing argument 1 of 'VOP_RMDIR_APV' from incompatible pointer type vnode_if.h: In function 'VOP_SYMLINK': vnode_if.h:723: warning: passing argument 1 of 'VOP_SYMLINK_APV' from incompatible pointer type vnode_if.h: In function 'VOP_READDIR': vnode_if.h:758: warning: passing argument 1 of 'VOP_READDIR_APV' from incompatible pointer type vnode_if.h: In function 'VOP_READLINK': vnode_if.h:784: warning: passing argument 1 of 'VOP_READLINK_APV' from incompatible pointer type vnode_if.h: In function 'VOP_INACTIVE': vnode_if.h:807: warning: passing argument 1 of 'VOP_INACTIVE_APV' from incompatible pointer type vnode_if.h: In function 'VOP_RECLAIM': vnode_if.h:830: warning: passing argument 1 of 'VOP_RECLAIM_APV' from incompatible pointer type vnode_if.h: In function 'VOP_LOCK1': vnode_if.h:859: warning: passing argument 1 of 'VOP_LOCK1_APV' from incompatible pointer type vnode_if.h: In function 'VOP_UNLOCK': vnode_if.h:882: warning: passing argument 1 of 'VOP_UNLOCK_APV' from incompatible pointer type vnode_if.h: In function 'VOP_BMAP': vnode_if.h:917: warning: passing argument 1 of 'VOP_BMAP_APV' from incompatible pointer type vnode_if.h: In function 'VOP_STRATEGY': vnode_if.h:940: warning: passing argument 1 of 'VOP_STRATEGY_APV' from incompatible pointer type vnode_if.h: In function 'VOP_GETWRITEMOUNT': vnode_if.h:963: warning: passing argument 1 of 'VOP_GETWRITEMOUNT_APV' from incompatible pointer type vnode_if.h: In function 'VOP_PRINT': vnode_if.h:983: warning: passing argument 1 of 'VOP_PRINT_APV' from incompatible pointer type vnode_if.h: In function 'VOP_PATHCONF': vnode_if.h:1009: warning: passing argument 1 of 'VOP_PATHCONF_APV' from incompatible pointer type vnode_if.h: In function 'VOP_ADVLOCK': vnode_if.h:1041: warning: passing argument 1 of 'VOP_ADVLOCK_APV' from incompatible pointer type vnode_if.h: In function 'VOP_ADVLOCKASYNC': vnode_if.h:1079: warning: passing argument 1 of 'VOP_ADVLOCKASYNC_APV' from incompatible pointer type vnode_if.h: In function 'VOP_REALLOCBLKS': vnode_if.h:1102: warning: passing argument 1 of 'VOP_REALLOCBLKS_APV' from incompatible pointer type vnode_if.h: In function 'VOP_GETPAGES': vnode_if.h:1134: warning: passing argument 1 of 'VOP_GETPAGES_APV' from incompatible pointer type vnode_if.h: In function 'VOP_PUTPAGES': vnode_if.h:1169: warning: passing argument 1 of 'VOP_PUTPAGES_APV' from incompatible pointer type vnode_if.h: In function 'VOP_GETACL': vnode_if.h:1201: warning: passing argument 1 of 'VOP_GETACL_APV' from incompatible pointer type vnode_if.h: In function 'VOP_SETACL': vnode_if.h:1233: warning: passing argument 1 of 'VOP_SETACL_APV' from incompatible pointer type vnode_if.h: In function 'VOP_ACLCHECK': vnode_if.h:1265: warning: passing argument 1 of 'VOP_ACLCHECK_APV' from incompatible pointer type vnode_if.h: In function 'VOP_CLOSEEXTATTR': vnode_if.h:1294: warning: passing argument 1 of 'VOP_CLOSEEXTATTR_APV' from incompatible pointer type vnode_if.h: In function 'VOP_GETEXTATTR': vnode_if.h:1332: warning: passing argument 1 of 'VOP_GETEXTATTR_APV' from incompatible pointer type vnode_if.h: In function 'VOP_LISTEXTATTR': vnode_if.h:1367: warning: passing argument 1 of 'VOP_LISTEXTATTR_APV' from incompatible pointer type vnode_if.h: In function 'VOP_OPENEXTATTR': vnode_if.h:1393: warning: passing argument 1 of 'VOP_OPENEXTATTR_APV' from incompatible pointer type vnode_if.h: In function 'VOP_DELETEEXTATTR': vnode_if.h:1425: warning: passing argument 1 of 'VOP_DELETEEXTATTR_APV' from incompatible pointer type vnode_if.h: In function 'VOP_SETEXTATTR': vnode_if.h:1460: warning: passing argument 1 of 'VOP_SETEXTATTR_APV' from incompatible pointer type vnode_if.h: In function 'VOP_SETLABEL': vnode_if.h:1489: warning: passing argument 1 of 'VOP_SETLABEL_APV' from incompatible pointer type vnode_if.h: In function 'VOP_VPTOFH': vnode_if.h:1512: warning: passing argument 1 of 'VOP_VPTOFH_APV' from incompatible pointer type vnode_if.h: In function 'VOP_VPTOCNP': vnode_if.h:1544: warning: passing argument 1 of 'VOP_VPTOCNP_APV' from incompatible pointer type In file included from sysctlfs_subr.c:16: vnode.h: At top level: vnode.h:551: warning: 'struct vop_lease_args' declared inside parameter list vnode.h:551: warning: its scope is only this definition or declaration, which is probably not what you want vnode.h:554: error: expected declaration specifiers or '...' before 'udev_t' vnode.h:568: warning: 'struct vop_lease_args' declared inside parameter list vnode.h:619: warning: 'struct vop_lock_args' declared inside parameter list vnode.h:622: warning: 'struct vop_lock_args' declared inside parameter list vnode.h:628: warning: 'struct vop_lock_args' declared inside parameter list vnode.h:636: warning: 'struct vop_createvobject_args' declared inside parameter list vnode.h:637: warning: 'struct vop_destroyvobject_args' declared inside parameter list vnode.h:638: warning: 'struct vop_getvobject_args' declared inside parameter list sysctlfs_subr.c: In function 'sysctlfs_allocvp': sysctlfs_subr.c:152: error: 'securelevel' undeclared (first use in this function) sysctlfs_subr.c:152: error: (Each undeclared identifier is reported only once sysctlfs_subr.c:152: error: for each function it appears in.) sysctlfs_subr.c:154: error: 'struct proc' has no member named 'p_prison' sysctlfs_subr.c: In function 'sysctlfs_rw': sysctlfs_subr.c:251: error: 'struct uio' has no member named 'uio_procp' sysctlfs_subr.c: In function 'sysctlfs_sysctl': sysctlfs_subr.c:353: error: 'struct sysctl_req' has no member named 'p' sysctlfs_subr.c:376: error: 'securelevel' undeclared (first use in this function) sysctlfs_subr.c:382: error: 'struct sysctl_req' has no member named 'p' sysctlfs_subr.c:383: warning: implicit declaration of function 'suser_xxx' sysctlfs_subr.c:383: warning: nested extern declaration of 'suser_xxx' sysctlfs_subr.c:383: error: 'struct sysctl_req' has no member named 'p' sysctlfs_subr.c:384: error: 'PRISON_ROOT' undeclared (first use in this function) *** Error code 1 Stop in /tmp/sysctlfs/sysctlfs. --- From owner-freebsd-fs@FreeBSD.ORG Wed Feb 23 12:45:43 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9EB6106566B for ; Wed, 23 Feb 2011 12:45:43 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 977458FC0C for ; Wed, 23 Feb 2011 12:45:43 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 3DF7546B0D; Wed, 23 Feb 2011 07:45:43 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.10]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 28EF38A01D; Wed, 23 Feb 2011 07:45:42 -0500 (EST) From: John Baldwin To: Bob Friesenhahn Date: Wed, 23 Feb 2011 07:37:36 -0500 User-Agent: KMail/1.13.5 (FreeBSD/7.4-CBSD-20110107; KDE/4.4.5; amd64; ; ) References: <201102211707.p1LH7c8n075660@lurza.secnetix.de> <201102220931.17733.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201102230737.36748.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Wed, 23 Feb 2011 07:45:42 -0500 (EST) X-Virus-Scanned: clamav-milter 0.96.3 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=0.5 required=4.2 tests=BAYES_00,MAY_BE_FORGED, RDNS_DYNAMIC autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on bigwig.baldwin.cx Cc: freebsd-fs@freebsd.org, Kelly Dean Subject: Re: Why is procfs deprecated in favor of procstat? 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, 23 Feb 2011 12:45:43 -0000 On Tuesday, February 22, 2011 2:10:57 pm Bob Friesenhahn wrote: > On Tue, 22 Feb 2011, John Baldwin wrote: > > > > Actually, the replacement for procfs is not sysctl, but ptrace(2), and there > > I have been following this discussion with my jaw agape. It seems > that the many men standing around this elephant are all perceiving > completely different things based on their own interests and > experiences. > > My own software is using procfs to efficiently determine the path to > the currently running executable. I am sure that other software does > the same since Linux procfs (and probably OS X) supports the same > mechanism. It is difficult to imagine how this would be done via > ptrace(2). It would not be the first syscall to return a path to userland (see __getcwd()). Presumably the reason a ptrace(2) OP has not been added for that is that it is that nothing that was ported from procfs to ptrace(2) has needed it. -- John Baldwin From owner-freebsd-fs@FreeBSD.ORG Wed Feb 23 13:15:48 2011 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7E011065670 for ; Wed, 23 Feb 2011 13:15:48 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id A73358FC1F for ; Wed, 23 Feb 2011 13:15:48 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 62B1146B1A; Wed, 23 Feb 2011 08:15:48 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.10]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 634AA8A027; Wed, 23 Feb 2011 08:15:47 -0500 (EST) From: John Baldwin To: fs@freebsd.org Date: Wed, 23 Feb 2011 08:11:32 -0500 User-Agent: KMail/1.13.5 (FreeBSD/7.4-CBSD-20110107; KDE/4.4.5; amd64; ; ) MIME-Version: 1.0 Message-Id: <201102230811.32864.jhb@freebsd.org> Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Wed, 23 Feb 2011 08:15:47 -0500 (EST) X-Virus-Scanned: clamav-milter 0.96.3 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Flag: YES X-Spam-Status: Yes, score=6.8 required=4.2 tests=BAYES_00,MAY_BE_FORGED, RDNS_DYNAMIC, TO_NO_BRKTS_DIRECT, TO_NO_BRKTS_DYNIP autolearn=no version=3.3.1 X-Spam-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 1.0 RDNS_DYNAMIC Delivered to internal network by host with * dynamic-looking rDNS * 1.4 MAY_BE_FORGED Relay IP's reverse DNS does not resolve to IP * 2.6 TO_NO_BRKTS_DIRECT To: misformatted and direct-to-MX * 3.7 TO_NO_BRKTS_DYNIP To: misformatted and dynamic rDNS X-Spam-Level: ****** X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on bigwig.baldwin.cx Cc: "Pedro F. Giffuni" Subject: Simple ext2fs allocation routine cleanups 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, 23 Feb 2011 13:15:48 -0000 I have some small changes to ext2fs to use ffs() to simplify some of the allocation routines. The changes compile, but I have not had time to generate a test ext2fs file system to run-test them. If someone has some spare cycles to setup a test file system and try them out I would appreciate it. Otherwise I will get to it eventually. Given that this hasn't been run-tested yet, I would not recommend using it for a production ext2fs since it may completely trash the filesystem. Index: ext2_alloc.c =================================================================== --- ext2_alloc.c (revision 218951) +++ ext2_alloc.c (working copy) @@ -815,16 +815,12 @@ } } i = start + len - loc; - map = ibp[i]; - ipref = i * NBBY; - for (i = 1; i < (1 << NBBY); i <<= 1, ipref++) { - if ((map & i) == 0) { - goto gotit; - } + map = ibp[i] ^ 0xff; + if (map == 0) { + printf("fs = %s\n", fs->e2fs_fsmnt); + panic("ext2fs_nodealloccg: block not in map"); } - printf("fs = %s\n", fs->e2fs_fsmnt); - panic("ext2fs_nodealloccg: block not in map"); - /* NOTREACHED */ + ipref = i * NBBY + ffs(map); gotit: setbit(ibp, ipref); EXT2_LOCK(ump); @@ -952,7 +948,6 @@ static daddr_t ext2_mapsearch(struct m_ext2fs *fs, char *bbp, daddr_t bpref) { - daddr_t bno; int start, len, loc, i, map; /* @@ -977,15 +972,12 @@ } } i = start + len - loc; - map = bbp[i]; - bno = i * NBBY; - for (i = 1; i < (1 << NBBY); i <<= 1, bno++) { - if ((map & i) == 0) - return (bno); + map = bbp[i] ^ 0xff; + if (map == 0) { + printf("fs = %s\n", fs->e2fs_fsmnt); + panic("ext2fs_mapsearch: block not in map"); } - printf("fs = %s\n", fs->e2fs_fsmnt); - panic("ext2fs_mapsearch: block not in map"); - /* NOTREACHED */ + return (i * NBBY + ffs(map)); } /* -- John Baldwin From owner-freebsd-fs@FreeBSD.ORG Wed Feb 23 14:02:46 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B6E9C106566C for ; Wed, 23 Feb 2011 14:02:46 +0000 (UTC) (envelope-from gnehzuil@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 87A3A8FC18 for ; Wed, 23 Feb 2011 14:02:46 +0000 (UTC) Received: by pzk32 with SMTP id 32so535829pzk.13 for ; Wed, 23 Feb 2011 06:02:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=fTvUWDpzDE5VUEXIanIqJqkfkvIbMtlzDpJNV+z8mgE=; b=kFMayIhQt1YIIQdc88P1U+xSVy/6JFiCQ4hOtITsUeIer9Wv0GqVGT5zV3he2gUPJN CDRW9bF8uhO8STOIKKx3DAC3J28jEaYjIeuh9pscDC1qhtYrZjmVGaR0HV9C2WDPehu5 wBahO3BGHX7cTe2ucTZSQlH9WJI8Gua+dFrF0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=TKcVQtRpMXVwtCGMTFXKQv8NsCk5Qnr889kucQKCG3TPvKWUiAK5cNenp/YqAl7q5U ywJW+aj91IrxJOeWJ1Gw3mICG3zid+OmFZrho9GtFpgOPqxeZbcdVXdSlM9mQldKu/Q3 3nYZDFmIgn9ML7h3hwb8+VF1T+0oQQaT49idA= Received: by 10.142.178.7 with SMTP id a7mr3198965wff.386.1298468014597; Wed, 23 Feb 2011 05:33:34 -0800 (PST) Received: from [192.168.1.157] ([166.111.68.197]) by mx.google.com with ESMTPS id z8sm5318886wfj.13.2011.02.23.05.33.32 (version=SSLv3 cipher=OTHER); Wed, 23 Feb 2011 05:33:33 -0800 (PST) Message-ID: <4D650CA5.4030603@gmail.com> Date: Wed, 23 Feb 2011 21:33:25 +0800 From: gnehzuil User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: John Baldwin References: <201102230811.32864.jhb@freebsd.org> In-Reply-To: <201102230811.32864.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: Simple ext2fs allocation routine cleanups 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, 23 Feb 2011 14:02:46 -0000 Hi John, I can try to do some tests. :-) Best regards, lz On 02/23/2011 09:11 PM, John Baldwin wrote: > I have some small changes to ext2fs to use ffs() to simplify some of the > allocation routines. The changes compile, but I have not had time to generate > a test ext2fs file system to run-test them. If someone has some spare cycles > to setup a test file system and try them out I would appreciate it. Otherwise > I will get to it eventually. Given that this hasn't been run-tested yet, I > would not recommend using it for a production ext2fs since it may completely > trash the filesystem. > > Index: ext2_alloc.c > =================================================================== > --- ext2_alloc.c (revision 218951) > +++ ext2_alloc.c (working copy) > @@ -815,16 +815,12 @@ > } > } > i = start + len - loc; > - map = ibp[i]; > - ipref = i * NBBY; > - for (i = 1; i< (1<< NBBY); i<<= 1, ipref++) { > - if ((map& i) == 0) { > - goto gotit; > - } > + map = ibp[i] ^ 0xff; > + if (map == 0) { > + printf("fs = %s\n", fs->e2fs_fsmnt); > + panic("ext2fs_nodealloccg: block not in map"); > } > - printf("fs = %s\n", fs->e2fs_fsmnt); > - panic("ext2fs_nodealloccg: block not in map"); > - /* NOTREACHED */ > + ipref = i * NBBY + ffs(map); > gotit: > setbit(ibp, ipref); > EXT2_LOCK(ump); > @@ -952,7 +948,6 @@ > static daddr_t > ext2_mapsearch(struct m_ext2fs *fs, char *bbp, daddr_t bpref) > { > - daddr_t bno; > int start, len, loc, i, map; > > /* > @@ -977,15 +972,12 @@ > } > } > i = start + len - loc; > - map = bbp[i]; > - bno = i * NBBY; > - for (i = 1; i< (1<< NBBY); i<<= 1, bno++) { > - if ((map& i) == 0) > - return (bno); > + map = bbp[i] ^ 0xff; > + if (map == 0) { > + printf("fs = %s\n", fs->e2fs_fsmnt); > + panic("ext2fs_mapsearch: block not in map"); > } > - printf("fs = %s\n", fs->e2fs_fsmnt); > - panic("ext2fs_mapsearch: block not in map"); > - /* NOTREACHED */ > + return (i * NBBY + ffs(map)); > } > > /* > From owner-freebsd-fs@FreeBSD.ORG Wed Feb 23 15:24:25 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4628106566B for ; Wed, 23 Feb 2011 15:24:25 +0000 (UTC) (envelope-from martin@lispworks.com) Received: from lwfs1-cam.cam.lispworks.com (mail.lispworks.com [193.34.186.230]) by mx1.freebsd.org (Postfix) with ESMTP id 7180E8FC12 for ; Wed, 23 Feb 2011 15:24:25 +0000 (UTC) Received: from higson.cam.lispworks.com (higson [192.168.1.7]) by lwfs1-cam.cam.lispworks.com (8.14.3/8.14.3) with ESMTP id p1NFDOcI021374; Wed, 23 Feb 2011 15:13:24 GMT (envelope-from martin@lispworks.com) Received: from higson.cam.lispworks.com (localhost.localdomain [127.0.0.1]) by higson.cam.lispworks.com (8.14.4) id p1NFDO4u031047; Wed, 23 Feb 2011 15:13:24 GMT Received: (from martin@localhost) by higson.cam.lispworks.com (8.14.4/8.14.4/Submit) id p1NFDOw4031044; Wed, 23 Feb 2011 15:13:24 GMT Date: Wed, 23 Feb 2011 15:13:24 GMT Message-Id: <201102231513.p1NFDOw4031044@higson.cam.lispworks.com> From: Martin Simmons To: freebsd-fs@freebsd.org In-reply-to: <20110222211444.GD78089@deviant.kiev.zoral.com.ua> (message from Kostik Belousov on Tue, 22 Feb 2011 23:14:44 +0200) References: <201102211707.p1LH7c8n075660@lurza.secnetix.de> <476667.58379.qm@web121516.mail.ne1.yahoo.com> <20110222095211.GA96223@icarus.home.lan> <201102220931.17733.jhb@freebsd.org> <20110222211444.GD78089@deviant.kiev.zoral.com.ua> Subject: Re: Why is procfs deprecated in favor of procstat? 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, 23 Feb 2011 15:24:25 -0000 >>>>> On Tue, 22 Feb 2011 23:14:44 +0200, Kostik Belousov said: > > On Tue, Feb 22, 2011 at 01:10:57PM -0600, Bob Friesenhahn wrote: > > On Tue, 22 Feb 2011, John Baldwin wrote: > > > > > >Actually, the replacement for procfs is not sysctl, but ptrace(2), and > > >there > > > > I have been following this discussion with my jaw agape. It seems > > that the many men standing around this elephant are all perceiving > > completely different things based on their own interests and > > experiences. > > > > My own software is using procfs to efficiently determine the path to > > the currently running executable. I am sure that other software does > > the same since Linux procfs (and probably OS X) supports the same > > mechanism. It is difficult to imagine how this would be done via > > ptrace(2). > Look at the PT_VM_TIMESTAMP + PT_VM_ENTRY. You would iterate over > the the mappings in the address space and look at the binaries at > pve_path, if any. The one that is elf object f the ET_EXEC type > is the binary. It is somewhat clumsy but the end result is the same > as if reading /proc//file. > > Or, you use sysctl kern.proc.vmmap and get essentially the same data. > PT_VM_ENTRY was added long after the sysctl, I did not objected exactly > because ptrace(2) looked more logical. > > The advantage of using procfs or sysctl instead of ptrace(2) is that > you do not need to attach as debugger, causing the issues with signal > delivery for the debugee. Another advantage I find of (linux) procfs is that you always get a textual version of it, which can be useful in shell scripts and debugging situations. /sbin/sysctl kern.proc.vmmap isn't usable because the command has no way to specify the pid. /usr/bin/procstat gives access to only part of the procfs and sysctl namespace. __Martin From owner-freebsd-fs@FreeBSD.ORG Wed Feb 23 15:35:55 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 47396106566B for ; Wed, 23 Feb 2011 15:35:55 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id D28848FC08 for ; Wed, 23 Feb 2011 15:35:54 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id p1NFYJ9B027407 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Feb 2011 17:34:19 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p1NFYJVM069613; Wed, 23 Feb 2011 17:34:19 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p1NFYJXv069612; Wed, 23 Feb 2011 17:34:19 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 23 Feb 2011 17:34:19 +0200 From: Kostik Belousov To: Martin Simmons Message-ID: <20110223153419.GQ78089@deviant.kiev.zoral.com.ua> References: <201102211707.p1LH7c8n075660@lurza.secnetix.de> <476667.58379.qm@web121516.mail.ne1.yahoo.com> <20110222095211.GA96223@icarus.home.lan> <201102220931.17733.jhb@freebsd.org> <20110222211444.GD78089@deviant.kiev.zoral.com.ua> <201102231513.p1NFDOw4031044@higson.cam.lispworks.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jwHhyFZm5GCAobZr" Content-Disposition: inline In-Reply-To: <201102231513.p1NFDOw4031044@higson.cam.lispworks.com> User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-fs@freebsd.org Subject: Re: Why is procfs deprecated in favor of procstat? 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, 23 Feb 2011 15:35:55 -0000 --jwHhyFZm5GCAobZr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 23, 2011 at 03:13:24PM +0000, Martin Simmons wrote: > >>>>> On Tue, 22 Feb 2011 23:14:44 +0200, Kostik Belousov said: > >=20 > > On Tue, Feb 22, 2011 at 01:10:57PM -0600, Bob Friesenhahn wrote: > > > On Tue, 22 Feb 2011, John Baldwin wrote: > > > > > > > >Actually, the replacement for procfs is not sysctl, but ptrace(2), a= nd > > > >there > > >=20 > > > I have been following this discussion with my jaw agape. It seems=20 > > > that the many men standing around this elephant are all perceiving=20 > > > completely different things based on their own interests and=20 > > > experiences. > > >=20 > > > My own software is using procfs to efficiently determine the path to= =20 > > > the currently running executable. I am sure that other software does= =20 > > > the same since Linux procfs (and probably OS X) supports the same=20 > > > mechanism. It is difficult to imagine how this would be done via=20 > > > ptrace(2). > > Look at the PT_VM_TIMESTAMP + PT_VM_ENTRY. You would iterate over > > the the mappings in the address space and look at the binaries at > > pve_path, if any. The one that is elf object f the ET_EXEC type > > is the binary. It is somewhat clumsy but the end result is the same > > as if reading /proc//file. > >=20 > > Or, you use sysctl kern.proc.vmmap and get essentially the same data. > > PT_VM_ENTRY was added long after the sysctl, I did not objected exactly > > because ptrace(2) looked more logical. > >=20 > > The advantage of using procfs or sysctl instead of ptrace(2) is that > > you do not need to attach as debugger, causing the issues with signal > > delivery for the debugee. >=20 > Another advantage I find of (linux) procfs is that you always get a textu= al > version of it, which can be useful in shell scripts and debugging situati= ons. >=20 > /sbin/sysctl kern.proc.vmmap isn't usable because the command has no way = to > specify the pid. >=20 > /usr/bin/procstat gives access to only part of the procfs and sysctl > namespace. Apparently, there is kern.proc.pathname sysctl and -b switch to procstat. I never claimed that sysctls are useful from the command line, rather, they form a binary interface for the programs. --jwHhyFZm5GCAobZr Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk1lKPoACgkQC3+MBN1Mb4h40QCfaX563yW53iGI6besxmMkbCcv gkMAn0aDetdGj8xoSnL8apFxJBDDE981 =tG46 -----END PGP SIGNATURE----- --jwHhyFZm5GCAobZr-- From owner-freebsd-fs@FreeBSD.ORG Wed Feb 23 16:48:49 2011 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 14BE81065670 for ; Wed, 23 Feb 2011 16:48:49 +0000 (UTC) (envelope-from gnehzuil@gmail.com) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id C45918FC13 for ; Wed, 23 Feb 2011 16:48:48 +0000 (UTC) Received: by yib19 with SMTP id 19so186908yib.13 for ; Wed, 23 Feb 2011 08:48:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=e35h/fdktp7J6WVJarRo0vbK6x0oUwXcjXgHuf6TXPg=; b=LFLR1xYNvoaESfw6lVxW9cULHpj0b/ZZGB5YFRxlaGpQB6yB7M/R7k5zJqFbgPi4V+ HsSbKmVP9wU57K2Tzxqgr7ZBJDYA4b/37GqOPIDaF+enzmnc5sV2Dl+/TCXKoLJkHEFm mpJBoJRTpnhX00ebGO8/Qfz92pu3ysRzN8GvE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=lOpCatqk3OqSJr13UUAYRc0z+rpK0ivznn66wAKhGIQZdtuKyGjN8k3OBqiXxOeWHJ VFxo3za/mMhUHOV9vH3zvXNoC0L62tY3ZocCzoteXX6cfCzvZSf20ZIN4gsMTPNkt76R i30Qd51AXN+S/6x3F0E3VYwkBHYfBTIPyBCbQ= MIME-Version: 1.0 Received: by 10.236.109.51 with SMTP id r39mr2111429yhg.66.1298478933960; Wed, 23 Feb 2011 08:35:33 -0800 (PST) Received: by 10.147.167.13 with HTTP; Wed, 23 Feb 2011 08:35:33 -0800 (PST) In-Reply-To: <201102230811.32864.jhb@freebsd.org> References: <201102230811.32864.jhb@freebsd.org> Date: Thu, 24 Feb 2011 00:35:33 +0800 Message-ID: From: gnehzuil gnehzuil To: John Baldwin Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "Pedro F. Giffuni" , fs@freebsd.org Subject: Re: Simple ext2fs allocation routine cleanups 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, 23 Feb 2011 16:48:49 -0000 Hi John, I use dbench program to do some tests for your changes. However, it causes kernel crash. The error is as follows: panic: __lockmgr_args: recursing on non recursive lockmgr ext2fs @ /usr/src/sys/kern/vfs_subr.c:2124 Best regards, lz 2011/2/23 John Baldwin > I have some small changes to ext2fs to use ffs() to simplify some of the > allocation routines. The changes compile, but I have not had time to > generate > a test ext2fs file system to run-test them. If someone has some spare > cycles > to setup a test file system and try them out I would appreciate it. > Otherwise > I will get to it eventually. Given that this hasn't been run-tested yet, I > would not recommend using it for a production ext2fs since it may > completely > trash the filesystem. > > Index: ext2_alloc.c > =================================================================== > --- ext2_alloc.c (revision 218951) > +++ ext2_alloc.c (working copy) > @@ -815,16 +815,12 @@ > } > } > i = start + len - loc; > - map = ibp[i]; > - ipref = i * NBBY; > - for (i = 1; i < (1 << NBBY); i <<= 1, ipref++) { > - if ((map & i) == 0) { > - goto gotit; > - } > + map = ibp[i] ^ 0xff; > + if (map == 0) { > + printf("fs = %s\n", fs->e2fs_fsmnt); > + panic("ext2fs_nodealloccg: block not in map"); > } > - printf("fs = %s\n", fs->e2fs_fsmnt); > - panic("ext2fs_nodealloccg: block not in map"); > - /* NOTREACHED */ > + ipref = i * NBBY + ffs(map); > gotit: > setbit(ibp, ipref); > EXT2_LOCK(ump); > @@ -952,7 +948,6 @@ > static daddr_t > ext2_mapsearch(struct m_ext2fs *fs, char *bbp, daddr_t bpref) > { > - daddr_t bno; > int start, len, loc, i, map; > > /* > @@ -977,15 +972,12 @@ > } > } > i = start + len - loc; > - map = bbp[i]; > - bno = i * NBBY; > - for (i = 1; i < (1 << NBBY); i <<= 1, bno++) { > - if ((map & i) == 0) > - return (bno); > + map = bbp[i] ^ 0xff; > + if (map == 0) { > + printf("fs = %s\n", fs->e2fs_fsmnt); > + panic("ext2fs_mapsearch: block not in map"); > } > - printf("fs = %s\n", fs->e2fs_fsmnt); > - panic("ext2fs_mapsearch: block not in map"); > - /* NOTREACHED */ > + return (i * NBBY + ffs(map)); > } > > /* > > -- > John Baldwin > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > -- Liu Zheng gnehzuil@gmail.com CNU NetLab Tsinghua CSCW From owner-freebsd-fs@FreeBSD.ORG Wed Feb 23 19:18:11 2011 Return-Path: Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 336D41065670 for ; Wed, 23 Feb 2011 19:18:11 +0000 (UTC) (envelope-from hugo@barafranca.com) Received: from mail.barafranca.com (mail.barafranca.com [67.213.67.47]) by mx1.freebsd.org (Postfix) with ESMTP id 067A28FC17 for ; Wed, 23 Feb 2011 19:18:10 +0000 (UTC) Received: from localhost (unknown [172.16.100.24]) by mail.barafranca.com (Postfix) with ESMTP id A4B98BB5; Wed, 23 Feb 2011 18:55:55 +0000 (UTC) X-Virus-Scanned: amavisd-new at barafranca.com Received: from mail.barafranca.com ([172.16.100.24]) by localhost (mail.barafranca.com [172.16.100.24]) (amavisd-new, port 10024) with ESMTP id cswFkNK5k-WL; Wed, 23 Feb 2011 18:55:14 +0000 (UTC) Received: from [10.100.2.100] (a94-132-11-116.cpe.netcabo.pt [94.132.11.116]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.barafranca.com (Postfix) with ESMTPSA id E8F41BA5; Wed, 23 Feb 2011 18:55:13 +0000 (UTC) Message-ID: <4D65582A.7020404@barafranca.com> Date: Wed, 23 Feb 2011 18:55:38 +0000 From: Hugo Silva User-Agent: Thunderbird 2.0.0.23 (X11/20091030) MIME-Version: 1.0 To: Jeremy Chadwick References: <457880.36028.qm@web121501.mail.ne1.yahoo.com> <201102211707.p1LH7c8n075660@lurza.secnetix.de> <20110221174100.GA77744@icarus.home.lan> In-Reply-To: <20110221174100.GA77744@icarus.home.lan> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.ORG, kellydeanch@yahoo.com Subject: Re: Why is procfs deprecated in favor of procstat? 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, 23 Feb 2011 19:18:11 -0000 > For years now I have been considering a sysctl filesystem (e.g. mounted > as /sysctl) which would solve this dilemma. Read-only might be a wise > choice for this too. But this is beyond my skill set at this time, and > the existing documentation/examples for a pseudo filesystem are really > not that great. > http://netbsd.gw.com/cgi-bin/man-cgi?mount_sysctlfs++NetBSD-current From owner-freebsd-fs@FreeBSD.ORG Wed Feb 23 19:32:40 2011 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B3E06106566B for ; Wed, 23 Feb 2011 19:32:40 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 8617B8FC1D for ; Wed, 23 Feb 2011 19:32:40 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 3EE7846B06; Wed, 23 Feb 2011 14:32:40 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.10]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 618DC8A009; Wed, 23 Feb 2011 14:32:39 -0500 (EST) From: John Baldwin To: gnehzuil gnehzuil Date: Wed, 23 Feb 2011 14:32:38 -0500 User-Agent: KMail/1.13.5 (FreeBSD/7.4-CBSD-20110107; KDE/4.4.5; amd64; ; ) References: <201102230811.32864.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201102231432.38902.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Wed, 23 Feb 2011 14:32:39 -0500 (EST) X-Virus-Scanned: clamav-milter 0.96.3 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=0.5 required=4.2 tests=BAYES_00,MAY_BE_FORGED, RDNS_DYNAMIC autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on bigwig.baldwin.cx Cc: "Pedro F. Giffuni" , fs@freebsd.org Subject: Re: Simple ext2fs allocation routine cleanups 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, 23 Feb 2011 19:32:40 -0000 On Wednesday, February 23, 2011 11:35:33 am gnehzuil gnehzuil wrote: > Hi John, > > I use dbench program to do some tests for your changes. However, it causes > kernel crash. The error is as follows: > > panic: __lockmgr_args: recursing on non recursive lockmgr ext2fs @ > /usr/src/sys/kern/vfs_subr.c:2124 I wasn't able to reproduce that, but I did have silly off-by-one bugs in the use of ffs() that should be fixed now: Index: ext2_alloc.c =================================================================== --- ext2_alloc.c (revision 218975) +++ ext2_alloc.c (working copy) @@ -815,16 +815,12 @@ ext2_nodealloccg(struct inode *ip, int cg, daddr_t } } i = start + len - loc; - map = ibp[i]; - ipref = i * NBBY; - for (i = 1; i < (1 << NBBY); i <<= 1, ipref++) { - if ((map & i) == 0) { - goto gotit; - } + map = ibp[i] ^ 0xff; + if (map == 0) { + printf("fs = %s\n", fs->e2fs_fsmnt); + panic("ext2fs_nodealloccg: block not in map"); } - printf("fs = %s\n", fs->e2fs_fsmnt); - panic("ext2fs_nodealloccg: block not in map"); - /* NOTREACHED */ + ipref = i * NBBY + ffs(map) - 1; gotit: setbit(ibp, ipref); EXT2_LOCK(ump); @@ -952,7 +948,6 @@ ext2_vfree(pvp, ino, mode) static daddr_t ext2_mapsearch(struct m_ext2fs *fs, char *bbp, daddr_t bpref) { - daddr_t bno; int start, len, loc, i, map; /* @@ -977,15 +972,12 @@ ext2_mapsearch(struct m_ext2fs *fs, char *bbp, dad } } i = start + len - loc; - map = bbp[i]; - bno = i * NBBY; - for (i = 1; i < (1 << NBBY); i <<= 1, bno++) { - if ((map & i) == 0) - return (bno); + map = bbp[i] ^ 0xff; + if (map == 0) { + printf("fs = %s\n", fs->e2fs_fsmnt); + panic("ext2fs_mapsearch: block not in map"); } - printf("fs = %s\n", fs->e2fs_fsmnt); - panic("ext2fs_mapsearch: block not in map"); - /* NOTREACHED */ + return (i * NBBY + ffs(map) - 1); } /* -- John Baldwin From owner-freebsd-fs@FreeBSD.ORG Thu Feb 24 02:59:29 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A8DB106566B for ; Thu, 24 Feb 2011 02:59:29 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id 4C3A78FC12 for ; Thu, 24 Feb 2011 02:59:29 +0000 (UTC) Received: from julian-mac.elischer.org (adsl-69-105-81-85.dsl.scrm01.pacbell.net [69.105.81.85]) (authenticated bits=0) by vps1.elischer.org (8.14.4/8.14.4) with ESMTP id p1O2Z8QN038530 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 23 Feb 2011 18:35:10 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <4D65C3D6.9060205@freebsd.org> Date: Wed, 23 Feb 2011 18:35:02 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-fs@freebsd.org, kellydeanch@yahoo.com References: <201102211707.p1LH7c8n075660@lurza.secnetix.de> In-Reply-To: <201102211707.p1LH7c8n075660@lurza.secnetix.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Oliver Fromme Subject: Re: Why is procfs deprecated in favor of procstat? 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, 24 Feb 2011 02:59:29 -0000 On 2/21/11 9:07 AM, Oliver Fromme wrote: > Kelly Dean wrote: > > http://ivoras.sharanet.org/freebsd/freebsd8.html says that > > procfs is deprecated in favor of procstat. But Plan 9 says > > that procfs is the right way to do things. > > Linux says the same. But it's irrelevant what they say. > FreeBSD is not Plan 9, and FreeBSD is not Linux. > > Procfs has a long history of security vulnerabilities and > other problems. I do not mount procfs on most machines > I'm responsible for, especially not on machines that have > user accounts or services that are not restricted to jails. > > I also think it is inefficient to let the kernel render > data to ASCII, and then have userland tools parse that > ASCII data again. That's ridiculous. I disagree. It was ridiculous when pdp-11s had 500,000 instructions per second but there are many cases to day where it is not ridiculous. I don't think that procfs is by definition bad, and I am no really sure where this "edict" has come from. At fusion-io we have abstracted the control stuff to export as sysctl when compiled in the freebsd driver and procfs in the linux driver. While sysctl is 'ok' I will admit that the procfs variant is a bit more convenient to use. simply because you can enumerate the damned tree without seeing all the contents. > There is no sane > reason for putting kernel data as ASCII text into a pseudo > file system. > > Best regards > Oliver > From owner-freebsd-fs@FreeBSD.ORG Thu Feb 24 03:50:08 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4DB3D106564A for ; Thu, 24 Feb 2011 03:50:08 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta12.emeryville.ca.mail.comcast.net (qmta12.emeryville.ca.mail.comcast.net [76.96.27.227]) by mx1.freebsd.org (Postfix) with ESMTP id 236C08FC17 for ; Thu, 24 Feb 2011 03:50:07 +0000 (UTC) Received: from omta01.emeryville.ca.mail.comcast.net ([76.96.30.11]) by qmta12.emeryville.ca.mail.comcast.net with comcast id Bfq51g0080EPchoACfq7lC; Thu, 24 Feb 2011 03:50:07 +0000 Received: from koitsu.dyndns.org ([98.248.33.18]) by omta01.emeryville.ca.mail.comcast.net with comcast id Bfq51g01U0PUQVN8Mfq5gB; Thu, 24 Feb 2011 03:50:06 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 45EAA9B427; Wed, 23 Feb 2011 19:50:05 -0800 (PST) Date: Wed, 23 Feb 2011 19:50:05 -0800 From: Jeremy Chadwick To: Hugo Silva Message-ID: <20110224035005.GA13141@icarus.home.lan> References: <457880.36028.qm@web121501.mail.ne1.yahoo.com> <201102211707.p1LH7c8n075660@lurza.secnetix.de> <20110221174100.GA77744@icarus.home.lan> <4D65582A.7020404@barafranca.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D65582A.7020404@barafranca.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@FreeBSD.ORG, kellydeanch@yahoo.com Subject: Re: Why is procfs deprecated in favor of procstat? 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, 24 Feb 2011 03:50:08 -0000 On Wed, Feb 23, 2011 at 06:55:38PM +0000, Hugo Silva wrote: > >For years now I have been considering a sysctl filesystem (e.g. mounted > >as /sysctl) which would solve this dilemma. Read-only might be a wise > >choice for this too. But this is beyond my skill set at this time, and > >the existing documentation/examples for a pseudo filesystem are really > >not that great. > > > > http://netbsd.gw.com/cgi-bin/man-cgi?mount_sysctlfs++NetBSD-current This is fantastic, except for the fact that it's abstracted by something called puffs. I took a look at the NetBSD source code for this (src/usr.sbin/puffs/mount_sysctlfs, tag netbsd-5) and puffs is absolutely required for it to work. http://netbsd.gw.com/cgi-bin/man-cgi?puffs+4+NetBSD-current http://netbsd.gw.com/cgi-bin/man-cgi?puffs+3+NetBSD-current Simply put, someone would have to port puffs for mount_sysctlfs to work on FreeBSD. There is already efforts underway to do that, but I have absolutely no idea what the status of it is: http://wiki.freebsd.org/SOC2009TatsianaSeveryna -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Thu Feb 24 04:16:54 2011 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EA5CE1065670; Thu, 24 Feb 2011 04:16:53 +0000 (UTC) (envelope-from gnehzuil@gmail.com) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id B24078FC0C; Thu, 24 Feb 2011 04:16:53 +0000 (UTC) Received: by pwj8 with SMTP id 8so138831pwj.13 for ; Wed, 23 Feb 2011 20:16:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=KxgHpQZi1iUvKEhfr7eQXyCzFEkmQZdwqeTo34mTA8s=; b=bvxcJwiqXdWbIymHHaSLyQC/CB2MFOC9SBgZDoXz0yBMBj9z26pfrbNMMVqZbH/XFz /A4OpEFV5CoFgbf8YJk7gRPgEvldrMZRKinmAx9hgMFwlPspycKZBupNJqLo6HJpf4GP nzM16I6qeq+Eps4tfN56qFlbyPvMDqhrE4dmA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=kJEGcPE9XyGWyLDManciWGhzFWgx+B4LKiyHQybEbBYaShAB8RXqoiucukjSR2rHD6 ZHCqwH2Le1o1rYnuHs42NFQGOlERuUV4L+AP0+qh2zPCPNPZl1pTr01Gy1r4RkeM1Wh+ 5DPz2sw5YfCnx1/z2QHevqYkIA1L/AmCDpd/Q= Received: by 10.142.191.17 with SMTP id o17mr293004wff.204.1298521013254; Wed, 23 Feb 2011 20:16:53 -0800 (PST) Received: from [192.168.1.157] ([166.111.68.197]) by mx.google.com with ESMTPS id w11sm11716087wfh.6.2011.02.23.20.16.50 (version=SSLv3 cipher=OTHER); Wed, 23 Feb 2011 20:16:51 -0800 (PST) Message-ID: <4D65DBAE.7010505@gmail.com> Date: Thu, 24 Feb 2011 12:16:46 +0800 From: gnehzuil User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: John Baldwin References: <201102230811.32864.jhb@freebsd.org> <201102231432.38902.jhb@freebsd.org> In-Reply-To: <201102231432.38902.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: "Pedro F. Giffuni" , fs@freebsd.org Subject: Re: Simple ext2fs allocation routine cleanups 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, 24 Feb 2011 04:16:54 -0000 Hi John, I have tried your changes again. It's ok. The error doesn't occurred. I think the problem is off-by-one bug. Best regards, lz On 02/24/2011 03:32 AM, John Baldwin wrote: > On Wednesday, February 23, 2011 11:35:33 am gnehzuil gnehzuil wrote: >> Hi John, >> >> I use dbench program to do some tests for your changes. However, it causes >> kernel crash. The error is as follows: >> >> panic: __lockmgr_args: recursing on non recursive lockmgr ext2fs @ >> /usr/src/sys/kern/vfs_subr.c:2124 > I wasn't able to reproduce that, but I did have silly off-by-one bugs in the > use of ffs() that should be fixed now: > > Index: ext2_alloc.c > =================================================================== > --- ext2_alloc.c (revision 218975) > +++ ext2_alloc.c (working copy) > @@ -815,16 +815,12 @@ ext2_nodealloccg(struct inode *ip, int cg, daddr_t > } > } > i = start + len - loc; > - map = ibp[i]; > - ipref = i * NBBY; > - for (i = 1; i< (1<< NBBY); i<<= 1, ipref++) { > - if ((map& i) == 0) { > - goto gotit; > - } > + map = ibp[i] ^ 0xff; > + if (map == 0) { > + printf("fs = %s\n", fs->e2fs_fsmnt); > + panic("ext2fs_nodealloccg: block not in map"); > } > - printf("fs = %s\n", fs->e2fs_fsmnt); > - panic("ext2fs_nodealloccg: block not in map"); > - /* NOTREACHED */ > + ipref = i * NBBY + ffs(map) - 1; > gotit: > setbit(ibp, ipref); > EXT2_LOCK(ump); > @@ -952,7 +948,6 @@ ext2_vfree(pvp, ino, mode) > static daddr_t > ext2_mapsearch(struct m_ext2fs *fs, char *bbp, daddr_t bpref) > { > - daddr_t bno; > int start, len, loc, i, map; > > /* > @@ -977,15 +972,12 @@ ext2_mapsearch(struct m_ext2fs *fs, char *bbp, dad > } > } > i = start + len - loc; > - map = bbp[i]; > - bno = i * NBBY; > - for (i = 1; i< (1<< NBBY); i<<= 1, bno++) { > - if ((map& i) == 0) > - return (bno); > + map = bbp[i] ^ 0xff; > + if (map == 0) { > + printf("fs = %s\n", fs->e2fs_fsmnt); > + panic("ext2fs_mapsearch: block not in map"); > } > - printf("fs = %s\n", fs->e2fs_fsmnt); > - panic("ext2fs_mapsearch: block not in map"); > - /* NOTREACHED */ > + return (i * NBBY + ffs(map) - 1); > } > > /* > From owner-freebsd-fs@FreeBSD.ORG Thu Feb 24 10:55:26 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1FB25106566B for ; Thu, 24 Feb 2011 10:55:26 +0000 (UTC) (envelope-from martin@lispworks.com) Received: from lwfs1-cam.cam.lispworks.com (mail.lispworks.com [193.34.186.230]) by mx1.freebsd.org (Postfix) with ESMTP id 9B5AD8FC18 for ; Thu, 24 Feb 2011 10:55:24 +0000 (UTC) Received: from higson.cam.lispworks.com (higson [192.168.1.7]) by lwfs1-cam.cam.lispworks.com (8.14.3/8.14.3) with ESMTP id p1OAtL2x020244; Thu, 24 Feb 2011 10:55:21 GMT (envelope-from martin@lispworks.com) Received: from higson.cam.lispworks.com (localhost.localdomain [127.0.0.1]) by higson.cam.lispworks.com (8.14.4) id p1OAtLCu024577; Thu, 24 Feb 2011 10:55:21 GMT Received: (from martin@localhost) by higson.cam.lispworks.com (8.14.4/8.14.4/Submit) id p1OAtL5W024574; Thu, 24 Feb 2011 10:55:21 GMT Date: Thu, 24 Feb 2011 10:55:21 GMT Message-Id: <201102241055.p1OAtL5W024574@higson.cam.lispworks.com> From: Martin Simmons To: freebsd-fs@freebsd.org In-reply-to: <4D65C3D6.9060205@freebsd.org> (message from Julian Elischer on Wed, 23 Feb 2011 18:35:02 -0800) References: <201102211707.p1LH7c8n075660@lurza.secnetix.de> <4D65C3D6.9060205@freebsd.org> Subject: Re: Why is procfs deprecated in favor of procstat? 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, 24 Feb 2011 10:55:26 -0000 >>>>> On Wed, 23 Feb 2011 18:35:02 -0800, Julian Elischer said: > > While sysctl is 'ok' I will admit that the procfs variant is a bit > more convenient to use. > simply because you can enumerate the damned tree without seeing all > the contents. If by contents you mean values then try the sysctl -N option (though that still does a recursive enumeration). __Martin From owner-freebsd-fs@FreeBSD.ORG Thu Feb 24 19:28:57 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BD6CB1065673 for ; Thu, 24 Feb 2011 19:28:57 +0000 (UTC) (envelope-from piotr.kucharski@42.pl) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 5E0AA8FC18 for ; Thu, 24 Feb 2011 19:28:56 +0000 (UTC) Received: by wwb31 with SMTP id 31so1166978wwb.31 for ; Thu, 24 Feb 2011 11:28:56 -0800 (PST) Received: by 10.216.81.69 with SMTP id l47mr1204591wee.56.1298575736099; Thu, 24 Feb 2011 11:28:56 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.5.74 with HTTP; Thu, 24 Feb 2011 11:28:16 -0800 (PST) X-Originating-IP: [172.28.208.100] In-Reply-To: References: From: Piotr Kucharski Date: Thu, 24 Feb 2011 20:28:16 +0100 Message-ID: To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 Subject: Re: very slow zfs scrub 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, 24 Feb 2011 19:28:57 -0000 I've eliminated GELI from the picture and simplified the setup to one ggate disk. # ggatec create -u 13 x.x.x.x /dev/zvol/storage/zvol/temp # zpool create testink /dev/ggate13 : copied some files onto it, 10G took 40 min, but it was from one network drive to another, I'll let it slide # dd if=/testink/file of=/dev/null bs=64k 128712704 bytes transferred in 2.256507 secs (57040687 bytes/sec) : reading is as I expected to be, fine # zpool scrub testink : wait a little for the command to finish # zpool status testink pool: testink state: ONLINE scan: scrub in progress since Thu Feb 24 17:45:27 2011 227M scanned out of 9.97G at 27.9K/s, 101h52m to go 0 repaired, 2.22% done config: NAME STATE READ WRITE CKSUM testink ONLINE 0 0 0 ggate13 ONLINE 0 0 0 Wow! What does scrub do that it slows ggate drive almost to halt? What can I do to fix it? From owner-freebsd-fs@FreeBSD.ORG Thu Feb 24 20:02:08 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9DFFF1065670 for ; Thu, 24 Feb 2011 20:02:08 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 2EE6B8FC1B for ; Thu, 24 Feb 2011 20:02:07 +0000 (UTC) Received: by fxm19 with SMTP id 19so1050524fxm.13 for ; Thu, 24 Feb 2011 12:02:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=gxT/EaJTk+wtz7gUX7zCEqv3hoSepyUCRb5P+Zf87tE=; b=fq5JuZdAM04zJ22jZw96dEOE3XSHLagxeIthX3huOp3FASHn4zp8bGhJAtCmgoutn9 0Hk0+AnKzQv02fLbCU/Nbl2wCyx7KkAQ8QbmXvzabI7w8UZFrCQ3yxsM+kyX17aP08gX a7PHQHUkPqMii7r0+QCtNAAKZ65BVlm5em8ek= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=l0hRob9KzWzcGtiI5GnAsdfPM9T6ErrJsSYqzyvMcsJuaemIdY2rSwQOc9bnIpZXR9 8lHUE9S+OIKr1TRUXfrCb5qmaC8If3OnBPVrKXqEvhgTew1RE5N/QjM9oEfjgbMtX3oD kL+0TGVoUHcg67ZB+SyPQzXBtWyAyb9A3kiVY= MIME-Version: 1.0 Received: by 10.223.114.209 with SMTP id f17mr1542679faq.136.1298577627130; Thu, 24 Feb 2011 12:00:27 -0800 (PST) Received: by 10.223.94.67 with HTTP; Thu, 24 Feb 2011 12:00:27 -0800 (PST) In-Reply-To: References: Date: Thu, 24 Feb 2011 14:00:27 -0600 Message-ID: From: Adam Vande More To: Piotr Kucharski Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: very slow zfs scrub 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, 24 Feb 2011 20:02:08 -0000 On Thu, Feb 24, 2011 at 1:28 PM, Piotr Kucharski wrote: > > Wow! What does scrub do that it slows ggate drive almost to halt? > > What can I do to fix it? > I think network latency is going to have huge impact on performance here. Have you tried any ggate or nic tuning? Would HAST be an option for you? I think it has more performance thought put into it. -- Adam Vande More From owner-freebsd-fs@FreeBSD.ORG Fri Feb 25 00:37:04 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 674EF1065673 for ; Fri, 25 Feb 2011 00:37:04 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 02ACF8FC14 for ; Fri, 25 Feb 2011 00:37:03 +0000 (UTC) Received: by wyb32 with SMTP id 32so1350207wyb.13 for ; Thu, 24 Feb 2011 16:37:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=+TmSPS4z0Ks9mH+dEhJDdO0shorSU+7uV1a5+0CmJBk=; b=a7SfQYmmrGj0oHLaYGM2IoXT55XZPSuxr6ZuIQ3yV79b+oiEdI9DrB+DXZ2agEwXIJ cvYsA7RfqB29k39w5PwGK3v3494P7BXZfkjOg7ww/I0vy4Fm+SYROf4oyPkxET35nUZS OA364zmC/bOr31Pt9rpEQvYzKpZRaEU13Vlf4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=FUgiE2FUZBSOXw/HdwaQ0h7Onhkurpk0OPM93DqfWR0qZ4WbvfH4GsxsL7gSXS7t4C eOqBeHUK/lDYXTe9ccZPdU9zYYVXT2BmibWtUt7vLUCSEk+L9eXS56yHvcowKiHqVlJS FEUBkdkk0HrEy/0qyvWifpbywehQ5hsZKexh4= MIME-Version: 1.0 Received: by 10.216.50.193 with SMTP id z43mr1454048web.49.1298594223010; Thu, 24 Feb 2011 16:37:03 -0800 (PST) Received: by 10.216.15.74 with HTTP; Thu, 24 Feb 2011 16:37:02 -0800 (PST) Date: Thu, 24 Feb 2011 16:37:02 -0800 Message-ID: From: Garrett Cooper To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Are ru_inblock/ru_oublock in struct rusage used in capturing all block/cluster activity? 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, 25 Feb 2011 00:37:04 -0000 Hi FS folks, I'm trying to get a better understanding of these two statistics recorded by getrusage(2): long ru_inblock; /* block input operations */ long ru_oublock; /* block output operations */ Are the block operations limited to filesystem access on disk, or do they also apply to filesystems not backed by physical media, like memory disks, tmpfs, etc? It looks like it applies to all vnode operations in areas (the kern/vfs_*.c files), so I would assume that it applies to non-physical backed filesystem access as well, but just to be sure I thought I would ask the experts. ru_inblock and ru_oublock summed together compose the ac_io statistic used by acct(2), so I'm curious as to whether or not the utility of acct(2) on non-physical media backed filesystems was intentional. Thanks, -Garrett PS As a bonus question, why is ac_io a float primitive if it's just a sum of two longs? From owner-freebsd-fs@FreeBSD.ORG Fri Feb 25 08:04:13 2011 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 57E97106564A; Fri, 25 Feb 2011 08:04:13 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2E2018FC15; Fri, 25 Feb 2011 08:04:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1P84DKV092677; Fri, 25 Feb 2011 08:04:13 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1P84C4x092673; Fri, 25 Feb 2011 08:04:12 GMT (envelope-from linimon) Date: Fri, 25 Feb 2011 08:04:12 GMT Message-Id: <201102250804.p1P84C4x092673@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/155010: [ntfs] ntfs-3g via iscsi using msk driver cause kernel panic 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, 25 Feb 2011 08:04:13 -0000 Old Synopsis: ntfs-3g via iscsi using msk driver cause kernel panic New Synopsis: [ntfs] ntfs-3g via iscsi using msk driver cause kernel panic Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Fri Feb 25 08:03:48 UTC 2011 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=155010 From owner-freebsd-fs@FreeBSD.ORG Fri Feb 25 12:58:42 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AFB6F106566B; Fri, 25 Feb 2011 12:58:42 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 80F9A8FC0A; Fri, 25 Feb 2011 12:58:42 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 2FC0946B1A; Fri, 25 Feb 2011 07:58:42 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.10]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 691A18A01D; Fri, 25 Feb 2011 07:58:41 -0500 (EST) From: John Baldwin To: freebsd-fs@freebsd.org Date: Fri, 25 Feb 2011 07:48:42 -0500 User-Agent: KMail/1.13.5 (FreeBSD/7.4-CBSD-20110107; KDE/4.4.5; amd64; ; ) References: <201102250804.p1P84C4x092673@freefall.freebsd.org> In-Reply-To: <201102250804.p1P84C4x092673@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201102250748.42364.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Fri, 25 Feb 2011 07:58:41 -0500 (EST) X-Virus-Scanned: clamav-milter 0.96.3 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=0.5 required=4.2 tests=BAYES_00,MAY_BE_FORGED, RDNS_DYNAMIC autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on bigwig.baldwin.cx Cc: freebsd-bugs@freebsd.org, linimon@freebsd.org Subject: Re: kern/155010: [ntfs] ntfs-3g via iscsi using msk driver cause kernel panic 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, 25 Feb 2011 12:58:42 -0000 On Friday, February 25, 2011 3:04:12 am linimon@freebsd.org wrote: > Old Synopsis: ntfs-3g via iscsi using msk driver cause kernel panic > New Synopsis: [ntfs] ntfs-3g via iscsi using msk driver cause kernel panic > > Responsible-Changed-From-To: freebsd-bugs->freebsd-fs > Responsible-Changed-By: linimon > Responsible-Changed-When: Fri Feb 25 08:03:48 UTC 2011 > Responsible-Changed-Why: > Over to maintainer(s). > > http://www.freebsd.org/cgi/query-pr.cgi?pr=155010 Actually, it claims to be an msk0 bug since it doesn't panic when using re0. However, we'd probably need a stack trace before it could be investigated further. -- John Baldwin From owner-freebsd-fs@FreeBSD.ORG Fri Feb 25 19:13:06 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C64DB106564A; Fri, 25 Feb 2011 19:13:06 +0000 (UTC) (envelope-from dieterbsd@engineer.com) Received: from imr-db01.mx.aol.com (imr-db01.mx.aol.com [205.188.91.95]) by mx1.freebsd.org (Postfix) with ESMTP id 84A608FC0A; Fri, 25 Feb 2011 19:13:06 +0000 (UTC) Received: from imo-da03.mx.aol.com (imo-da03.mx.aol.com [205.188.169.201]) by imr-db01.mx.aol.com (8.14.1/8.14.1) with ESMTP id p1PJ2K7A003056; Fri, 25 Feb 2011 14:02:20 -0500 Received: from dieterbsd@engineer.com by imo-da03.mx.aol.com (mail_out_v42.9.) id n.f66.ef72306 (55713); Fri, 25 Feb 2011 14:02:17 -0500 (EST) Received: from smtprly-ma02.mx.aol.com (smtprly-ma02.mx.aol.com [64.12.207.141]) by cia-md01.mx.aol.com (v129.9) with ESMTP id MAILCIAMD014-5c524d67fcad35b; Fri, 25 Feb 2011 14:02:10 -0500 Received: from web-mmc-d05 (web-mmc-d05.sim.aol.com [205.188.103.95]) by smtprly-ma02.mx.aol.com (v129.9) with ESMTP id MAILSMTPRLYMA028-5c524d67fcad35b; Fri, 25 Feb 2011 14:02:05 -0500 To: kostikbel@gmail.com, freebsd-hackers@freebsd.org, freebsd-fs@freebsd.org Content-Transfer-Encoding: quoted-printable Date: Fri, 25 Feb 2011 14:02:05 -0500 X-AOL-IP: 67.206.162.62 X-MB-Message-Source: WebUI Received: from 67.206.162.62 by web-mmc-d05.sysops.aol.com (205.188.103.95) with HTTP (WebMailUI); Fri, 25 Feb 2011 14:02:05 -0500 MIME-Version: 1.0 From: dieterbsd@engineer.com X-MB-Message-Type: User Content-Type: text/plain; charset="us-ascii"; format=flowed X-Mailer: Mail.com Webmail 33298-STANDARD Message-Id: <8CDA335A0CABF7E-338-9FC4@web-mmc-d05.sysops.aol.com> X-Spam-Flag: NO X-AOL-SENDER: dieterbsd@engineer.com Cc: brucec@freebsd.org Subject: quotas an essential feature? (was: svn commit: r218953 - stable/8/usr.sbin/sysinstall) 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, 25 Feb 2011 19:13:06 -0000 > I promise to enable UFS quotas in GENERIC in one week unless anybody=20 objects > now. Huh? I thought GENERIC was supposed to include everything you needed to boot, not every possible feature that someone might desire? But requests to include things required to boot get rejected and nonessential features like quotas get added. WTF? From owner-freebsd-fs@FreeBSD.ORG Fri Feb 25 23:57:09 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B82E9106566C; Fri, 25 Feb 2011 23:57:09 +0000 (UTC) (envelope-from prvs=10374d3e62=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 01EF38FC08; Fri, 25 Feb 2011 23:57:08 +0000 (UTC) X-MDAV-Processed: mail1.multiplay.co.uk, Fri, 25 Feb 2011 23:46:15 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Fri, 25 Feb 2011 23:46:15 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-5.0 required=6.0 tests=USER_IN_WHITELIST shortcircuit=ham autolearn=disabled version=3.2.5 Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50012318159.msg; Fri, 25 Feb 2011 23:46:15 +0000 X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=10374d3e62=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: <317BD8618FA7450ABC86001948F4DFE4@multiplay.co.uk> From: "Steven Hartland" To: , , , References: <8CDA335A0CABF7E-338-9FC4@web-mmc-d05.sysops.aol.com> Date: Fri, 25 Feb 2011 23:46:30 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994 Cc: brucec@freebsd.org Subject: Re: quotas an essential feature? (was: svn commit: r218953 - stable/8/usr.sbin/sysinstall) 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, 25 Feb 2011 23:57:09 -0000 While I can understand some may want its not something we use on any of our machines, and I suspect that's the case for many others. Given adding it means the kernel will be doing extra work and hence a drop in performance for a feature most will never use, I'm guessing here, I would say just leave it out of generic unless there is a real pressing requirement for it? Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-fs@FreeBSD.ORG Sat Feb 26 07:49:31 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 185441065674; Sat, 26 Feb 2011 07:49:31 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id CD1FE8FC1A; Sat, 26 Feb 2011 07:49:30 +0000 (UTC) Received: by iwn33 with SMTP id 33so1940573iwn.13 for ; Fri, 25 Feb 2011 23:49:30 -0800 (PST) Received: by 10.42.218.134 with SMTP id hq6mr1873491icb.289.1298705104301; Fri, 25 Feb 2011 23:25:04 -0800 (PST) Received: from [192.168.2.119] (99-74-169-43.lightspeed.sntcca.sbcglobal.net [99.74.169.43]) by mx.google.com with ESMTPS id wt14sm1096803icb.4.2011.02.25.23.25.01 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 25 Feb 2011 23:25:03 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Tim Kientzle X-Priority: 3 In-Reply-To: <317BD8618FA7450ABC86001948F4DFE4@multiplay.co.uk> Date: Fri, 25 Feb 2011 23:25:00 -0800 Content-Transfer-Encoding: 7bit Message-Id: <98FE1AB5-5276-4B12-A034-106330EBB713@kientzle.com> References: <8CDA335A0CABF7E-338-9FC4@web-mmc-d05.sysops.aol.com> <317BD8618FA7450ABC86001948F4DFE4@multiplay.co.uk> To: Steven Hartland X-Mailer: Apple Mail (2.1082) Cc: freebsd-fs@freebsd.org, freebsd-hackers Subject: Re: quotas an essential feature? (was: svn commit: r218953 - stable/8/usr.sbin/sysinstall) 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, 26 Feb 2011 07:49:31 -0000 On Feb 25, 2011, at 3:46 PM, Steven Hartland wrote: > While I can understand some may want its not something we use on any of > our machines, and I suspect that's the case for many others. > > Given adding it means the kernel will be doing extra work and hence a > drop in performance... Does anyone have benchmark results to measure the performance hit? Tim From owner-freebsd-fs@FreeBSD.ORG Sat Feb 26 08:42:13 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 27B49106564A for ; Sat, 26 Feb 2011 08:42:13 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by mx1.freebsd.org (Postfix) with ESMTP id C5FA78FC08 for ; Sat, 26 Feb 2011 08:42:12 +0000 (UTC) Received: from omta03.westchester.pa.mail.comcast.net ([76.96.62.27]) by qmta09.westchester.pa.mail.comcast.net with comcast id CYiD1g0010bG4ec59YiDus; Sat, 26 Feb 2011 08:42:13 +0000 Received: from koitsu.dyndns.org ([98.248.33.18]) by omta03.westchester.pa.mail.comcast.net with comcast id CYiB1g0090PUQVN3PYiBvG; Sat, 26 Feb 2011 08:42:12 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 0AF279B422; Sat, 26 Feb 2011 00:42:10 -0800 (PST) Date: Sat, 26 Feb 2011 00:42:10 -0800 From: Jeremy Chadwick To: Tim Kientzle Message-ID: <20110226084210.GA24248@icarus.home.lan> References: <8CDA335A0CABF7E-338-9FC4@web-mmc-d05.sysops.aol.com> <317BD8618FA7450ABC86001948F4DFE4@multiplay.co.uk> <98FE1AB5-5276-4B12-A034-106330EBB713@kientzle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <98FE1AB5-5276-4B12-A034-106330EBB713@kientzle.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org, freebsd-hackers Subject: Re: quotas an essential feature? (was: svn commit: r218953 - stable/8/usr.sbin/sysinstall) 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, 26 Feb 2011 08:42:13 -0000 On Fri, Feb 25, 2011 at 11:25:00PM -0800, Tim Kientzle wrote: > On Feb 25, 2011, at 3:46 PM, Steven Hartland wrote: > > > While I can understand some may want its not something we use on any of > > our machines, and I suspect that's the case for many others. > > > > Given adding it means the kernel will be doing extra work and hence a > > drop in performance... > > Does anyone have benchmark results to measure the performance hit? I imagine there wouldn't be any (or extremely negligible) unless you used quotaon(8). -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Sat Feb 26 09:17:03 2011 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2CBB3106564A; Sat, 26 Feb 2011 09:17:03 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 02FEF8FC0C; Sat, 26 Feb 2011 09:17:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1Q9H2EH066594; Sat, 26 Feb 2011 09:17:02 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1Q9H2AB066590; Sat, 26 Feb 2011 09:17:02 GMT (envelope-from linimon) Date: Sat, 26 Feb 2011 09:17:02 GMT Message-Id: <201102260917.p1Q9H2AB066590@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-fs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/155010: [msk] ntfs-3g via iscsi using msk driver cause kernel panic 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, 26 Feb 2011 09:17:03 -0000 Old Synopsis: [ntfs] ntfs-3g via iscsi using msk driver cause kernel panic New Synopsis: [msk] ntfs-3g via iscsi using msk driver cause kernel panic Responsible-Changed-From-To: freebsd-fs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sat Feb 26 09:16:34 UTC 2011 Responsible-Changed-Why: reclassify per jhb. http://www.freebsd.org/cgi/query-pr.cgi?pr=155010