From owner-freebsd-fs@FreeBSD.ORG Sun Mar 19 00:10:57 2006 Return-Path: X-Original-To: fs@freebsd.org Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD2E516A420 for ; Sun, 19 Mar 2006 00:10:57 +0000 (UTC) (envelope-from rick@snowhite.cis.uoguelph.ca) Received: from dargo.cs.uoguelph.ca (dargo.cs.uoguelph.ca [131.104.94.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42D2543D48 for ; Sun, 19 Mar 2006 00:10:57 +0000 (GMT) (envelope-from rick@snowhite.cis.uoguelph.ca) Received: from snowhite.cis.uoguelph.ca (snowhite.cis.uoguelph.ca [131.104.48.1]) by dargo.cs.uoguelph.ca (8.13.1/8.13.1) with ESMTP id k2J0AtHG019750 for ; Sat, 18 Mar 2006 19:10:55 -0500 Received: (from rick@localhost) by snowhite.cis.uoguelph.ca (8.9.3/8.9.3) id TAA18779 for fs@freebsd.org; Sat, 18 Mar 2006 19:12:01 -0500 (EST) Date: Sat, 18 Mar 2006 19:12:01 -0500 (EST) From: rick@snowhite.cis.uoguelph.ca Message-Id: <200603190012.TAA18779@snowhite.cis.uoguelph.ca> To: fs@freebsd.org X-Scanned-By: MIMEDefang 2.52 on 131.104.94.197 Cc: Subject: NFSv4 server update 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, 19 Mar 2006 00:10:57 -0000 Just in case someone is interested, I've put up a new set of tarballs for my NFSv2,3,4 server for FreeBSD (along with an OpenBSD3.8 only client). There have been a couple of major bugfixes and a few minor enhancements as a result of testing at Connectathon 2006. The ftp site is: ftp.cis.uoguelph.ca/pub/nfsv4 and a primitive web page is at www.cis.uoguelph.ca/~nfsv4. Good luck with it, if you try it, rick ps: I don't anticipate further server changes until I get some 4.1 features rolled into it, and that will be quite a while. From owner-freebsd-fs@FreeBSD.ORG Sun Mar 19 04:19:06 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 56D6816A400 for ; Sun, 19 Mar 2006 04:19:06 +0000 (UTC) (envelope-from jofsama@yahoo.com) Received: from smtp010.mail.ukl.yahoo.com (smtp010.mail.ukl.yahoo.com [217.12.11.79]) by mx1.FreeBSD.org (Postfix) with SMTP id A487443D49 for ; Sun, 19 Mar 2006 04:19:05 +0000 (GMT) (envelope-from jofsama@yahoo.com) Received: (qmail 52224 invoked from network); 19 Mar 2006 04:19:04 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:Message-ID:Date:From:User-Agent:X-Accept-Language:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding; b=3MGaH1WPbqFs7sENG2BXDeCFQvxvVVNaqO5DrtdhuAHDPEeNBYPDhO1vDnZsboN/fL291MRLZMd2FGzskYZ7eiXfQdVSDX/ZnlezVUz50f0KN+Eq3TrnISmaGYMf8V4Ry3VbeJzTP+UNHNahRj7D9bBLOg6qX7cgdLRy/ABjYUg= ; Received: from unknown (HELO ?192.168.11.4?) (jofsama@220.98.11.46 with plain) by smtp010.mail.ukl.yahoo.com with SMTP; 19 Mar 2006 04:19:04 -0000 Message-ID: <441CDC20.7090300@yahoo.com> Date: Sun, 19 Mar 2006 13:20:48 +0900 From: Jarrod User-Agent: Mozilla Thunderbird 1.0.7 (X11/20060107) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Hard Disk Partitions & "mount" 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, 19 Mar 2006 04:19:06 -0000 Hi to mount & fdisk gurus, Wondering if anyone might have come across this or knows the reasoning behind this? I have an external USB HDD with 4 partitions (slices): 1: 60GB NTFS 2: 60GB NTFS 3: 60GB UFS2 [split into two 30GB freebsd partitions) 4: 58GB FAT32 All partitions were originally created (using Acronis PartExp) inside a single extended partition. I later changed the 3rd partition from being a logical partition to being a physical, leading to 2 entries in my MBR. One for the extended partition and one for the converted physical partition. Note that since I didn't modify the 4th logical partition, it came about that the extended partition was now spanning across (but skipping over) the physical 3rd partition. I converted the 3rd partition from type NTFS to FreeBSD using FreeBSD fdisk, which incidentally wiped out my logical partition entry in the MBR. Details on this and how I fixed it are in the freebsd-questions mailing list. What happens now is that if I mount any of the logical partitions (NTFS or FAT32 partitions) in the extended then I am completely unable to mount my FreeBSD (UFS) partitions. I am able to read off sectors from the partition (/dev/da0s2) using "dd", and also fdisk will read the ExtBootPartitionRecord ok, but fdisk is unable to write to it, complaining, "Cannot access consumer". If I unmount all the logical partitions then things are now suddenly ok and I can mount my UFS ones. Can you tell me why this is so? I am guessing the work-around is to trim down my extended partition so it does NOT overlap the physical UFS. Creating a second physical partition (3rd entry in the MBR) in the process in order to access the FAT32. Why does FreeBSD have this limitation? Is it necessary? Any and all input (academic or otherwise) greatly appreciated. Yours Sincerely, Jarrod. From owner-freebsd-fs@FreeBSD.ORG Sun Mar 19 18:19:58 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1495116A420; Sun, 19 Mar 2006 18:19:58 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id B41B843D45; Sun, 19 Mar 2006 18:19:57 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 833AB1A3C30; Sun, 19 Mar 2006 10:19:57 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 4ED05517B6; Sun, 19 Mar 2006 13:19:56 -0500 (EST) Date: Sun, 19 Mar 2006 13:19:53 -0500 From: Kris Kennaway To: Daichi GOTO Message-ID: <20060319181953.GA3999@xor.obsecurity.org> References: <43E5D052.3020207@freebsd.org> <43E656C7.8040302@freesbie.org> <43E6D5C8.4050405@freebsd.org> <43E71485.5040901@freesbie.org> <43E73330.8070101@freebsd.org> <43EB4C00.2030101@freebsd.org> <4417DD8D.3050201@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline In-Reply-To: <4417DD8D.3050201@freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: ozawa@ongs.co.jp, freebsd-hackers@freebsd.org, freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Alexander@Leidinger.net Subject: Re: patchset-9 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010) 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, 19 Mar 2006 18:19:58 -0000 --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Mar 15, 2006 at 06:25:33PM +0900, Daichi GOTO wrote: > I have updated the patchset-9 of unionfs. Another panic, this time from umount -f: panic: union_lock: wrong vnode (un == null) db> wh Tracing pid 17750 tid 100151 td 0xc7c38a20 kdb_enter(c07273ef,2,c0720d69,ee2d2aa0,c7c38a20) at kdb_enter+0x30 panic(c0720d69,c0599f59,c0599bef,ee2d2ab8,c07605c0) at panic+0x13f union_lock(ee2d2afc,0,0,2002,ca29ed20) at union_lock+0x68 VOP_LOCK_APV(c07605c0,ee2d2afc,ca29ede8,c6643488,8d3) at VOP_LOCK_APV+0xa6 vn_lock(ca29ed20,2002,c7c38a20,8d3,c6643488) at vn_lock+0xd3 vflush(c6643400,1,2,c7c38a20,c666bd80) at vflush+0x186 unionfs_unmount(c6643400,8080000,c7c38a20,c7c38a20,0) at unionfs_unmount+0x54 dounmount(c6643400,8080000,c7c38a20,415,800ff05) at dounmount+0x338 unmount(c7c38a20,ee2d2d04,c074769a,3ed,c69ea738) at unmount+0x270 syscall(3b,3b,3b,804a625,a000aa1) at syscall+0x2ea Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (22, FreeBSD ELF32, unmount), eip = 0x280c54c3, esp = 0xbfbfe44c, ebp = 0xbfbfe508 --- db> show lockedvnods Locked vnodes 0xc7347d20: tag ufs, type VLNK usecount 0, writecount 0, refcount 1 mountedhere 0 flags () lock type ufs: EXCL (count 1) by thread 0xc692c360 (pid 17230)#0 0xc05274eb at lockmgr+0x587 #1 0xc0594a97 at vop_stdlock+0x32 #2 0xc06fda82 at VOP_LOCK_APV+0xa6 #3 0xc066b4a1 at ffs_lock+0x19 #4 0xc06fda82 at VOP_LOCK_APV+0xa6 #5 0xc05ad540 at vn_lock+0xd3 #6 0xc059f500 at vrele+0x149 #7 0xc04ef97f at union_hashrem+0x28c #8 0xc04f4257 at union_reclaim+0x1b #9 0xc06fd958 at VOP_RECLAIM_APV+0xc4 #10 0xc05a02cc at vgonel+0x1b2 #11 0xc059cd48 at vtryrecycle+0x135 #12 0xc059c64b at vnlru_free+0x18e #13 0xc059cdce at getnewvnode+0x47 #14 0xc066a126 at ffs_vget+0xfc #15 0xc0671b7b at ufs_lookup+0xb83 #16 0xc06fb53d at VOP_CACHEDLOOKUP_APV+0xc4 #17 0xc0592219 at vfs_cache_lookup+0xcb ino 297887, on dev da0s1e 0xcb5d52a0: tag ufs, type VDIR usecount 3, writecount 0, refcount 6 mountedhere 0 flags () v_object 0xc8fa2d20 ref 0 pages 1 lock type ufs: EXCL (count 1) by thread 0xc692c360 (pid 17230)#0 0xc05274eb at lockmgr+0x587 #1 0xc0594a97 at vop_stdlock+0x32 #2 0xc06fda82 at VOP_LOCK_APV+0xa6 #3 0xc066b4a1 at ffs_lock+0x19 #4 0xc06fda82 at VOP_LOCK_APV+0xa6 #5 0xc05ad540 at vn_lock+0xd3 #6 0xc0596ba5 at lookup+0xe5 #7 0xc05967f9 at namei+0x434 #8 0xc05a69c6 at kern_lstat+0x4f #9 0xc05a6951 at lstat+0x2f #10 0xc06e4c52 at syscall+0x2ea #11 0xc06cebef at Xint0x80_syscall+0x1f ino 3044707, on dev da0s1e 0xc6d66540: tag ufs, type VDIR usecount 1, writecount 0, refcount 3 mountedhere 0xc6643400 flags () lock type ufs: EXCL (count 1) by thread 0xc7c38a20 (pid 17750)#0 0xc05274eb at lockmgr+0x587 #1 0xc0594a97 at vop_stdlock+0x32 #2 0xc06fda82 at VOP_LOCK_APV+0xa6 #3 0xc066b4a1 at ffs_lock+0x19 #4 0xc06fda82 at VOP_LOCK_APV+0xa6 #5 0xc05ad540 at vn_lock+0xd3 #6 0xc0599c72 at dounmount+0x51 #7 0xc0599bef at unmount+0x270 #8 0xc06e4c52 at syscall+0x2ea #9 0xc06cebef at Xint0x80_syscall+0x1f ino 612352, on dev da0s1d 0xca29ed20: tag unionfs, type VLNK usecount 0, writecount 0, refcount 2 mountedhere 0 flags (VI_DOOMED) VI_LOCKed lock type unionfs: EXCL (count 1) by thread 0xc692c360 (pid 17230)#0 0xc05274eb at lockmgr+0x587 #1 0xc04ef789 at union_hashrem+0x96 #2 0xc04f4257 at union_reclaim+0x1b #3 0xc06fd958 at VOP_RECLAIM_APV+0xc4 #4 0xc05a02cc at vgonel+0x1b2 #5 0xc059cd48 at vtryrecycle+0x135 #6 0xc059c64b at vnlru_free+0x18e #7 0xc059cdce at getnewvnode+0x47 #8 0xc066a126 at ffs_vget+0xfc #9 0xc0671b7b at ufs_lookup+0xb83 #10 0xc06fb53d at VOP_CACHEDLOOKUP_APV+0xc4 #11 0xc0592219 at vfs_cache_lookup+0xcb #12 0xc06fb43b at VOP_LOOKUP_APV+0xa6 #13 0xc0596f3a at lookup+0x47a #14 0xc05967f9 at namei+0x434 #15 0xc05a69c6 at kern_lstat+0x4f #16 0xc05a6951 at lstat+0x2f #17 0xc06e4c52 at syscall+0x2ea Kris --17pEHd4RhPHOinZp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEHaDIWry0BWjoQKURAnRyAJ9wZ0hBTj5EZADR+QLo8I2ccCiy4wCfTbDH qj5OwBVB+R8egMN1GQaWJKY= =4aeB -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp-- From owner-freebsd-fs@FreeBSD.ORG Mon Mar 20 07:17:53 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 22C9616A425; Mon, 20 Mar 2006 07:17:53 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from natial.ongs.co.jp (natial.ongs.co.jp [202.216.232.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B38F43D48; Mon, 20 Mar 2006 07:17:52 +0000 (GMT) (envelope-from daichi@freebsd.org) Received: from [192.168.1.101] (dullmdaler.ongs.co.jp [202.216.232.62]) by natial.ongs.co.jp (Postfix) with ESMTP id EECC5244C19; Mon, 20 Mar 2006 16:17:50 +0900 (JST) Message-ID: <441E571E.8040602@freebsd.org> Date: Mon, 20 Mar 2006 16:17:50 +0900 From: Daichi GOTO User-Agent: Thunderbird 1.5 (X11/20060310) MIME-Version: 1.0 To: Kris Kennaway References: <43E5D052.3020207@freebsd.org> <43E656C7.8040302@freesbie.org> <43E6D5C8.4050405@freebsd.org> <43E71485.5040901@freesbie.org> <43E73330.8070101@freebsd.org> <43EB4C00.2030101@freebsd.org> <4417DD8D.3050201@freebsd.org> <20060319181953.GA3999@xor.obsecurity.org> In-Reply-To: <20060319181953.GA3999@xor.obsecurity.org> Content-Type: text/plain; charset=Shift_JIS Content-Transfer-Encoding: 7bit Cc: ozawa@ongs.co.jp, freebsd-hackers@freebsd.org, Daichi GOTO , freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Alexander@Leidinger.net Subject: Re: patchset-9 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010) 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, 20 Mar 2006 07:17:53 -0000 Kris Kennaway wrote: > On Wed, Mar 15, 2006 at 06:25:33PM +0900, Daichi GOTO wrote: >> I have updated the patchset-9 of unionfs. > > Another panic, this time from umount -f: Thanks for your reports, Kris. OKay, we'll try to fix those panic problems when we have time :) -- Daichi GOTO, http://people.freebsd.org/~daichi From owner-freebsd-fs@FreeBSD.ORG Mon Mar 20 11:32:24 2006 Return-Path: X-Original-To: fs@freebsd.org Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A0FB16A401 for ; Mon, 20 Mar 2006 11:32:24 +0000 (UTC) (envelope-from knoll@edv-design.at) Received: from smtpout.internic.at (smtpout.internic.at [212.126.64.21]) by mx1.FreeBSD.org (Postfix) with SMTP id A7DAF43D6B for ; Mon, 20 Mar 2006 11:32:12 +0000 (GMT) (envelope-from knoll@edv-design.at) Received: from unknown ([80.108.175.25]) by smtpout.internic.at ; Mon Mar 20 12:32:09 2006 x-fsavag4mse-ts: a234ea8fdd13cc04 Content-Class: urn:content-classes:message Keywords: disclaimer Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Content-Type: multipart/related; type="multipart/alternative"; boundary="----_=_NextPart_001_01C64C11.E455DC28" Date: Mon, 20 Mar 2006 12:31:48 +0100 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Drivers and Failover on IBM Storage DS4800 and DS8000 thread-index: AcZMEd/w0S1dQfwyS8OyvMpOYt1jYg== From: "Ing. Alfred Knoll" To: , X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Drivers and Failover on IBM Storage DS4800 and DS8000 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, 20 Mar 2006 11:32:24 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01C64C11.E455DC28 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello =20 I am looking for actuallly freebsd-server running on an IBM DS4800 = and/or DS8000. If so, what release is in use? 1. Are this driver stable? 2. Does this Driver support failover to an alternate path to the = Storagebox ( Server with one HBA) On the official IBM -Support list is no statement =20 I am lookintg forward for positiv answers Alfred Knoll =20 =20 =20 =20 EDV-Design Informationstechnologie GmbH Br=FCnner Stra=DFe 192/1/1, A-1210 Wien Tel: +43 1 29 22 165-50 Fax: +43 1 29 22 165-90 Mobil: +43 660 4614996 E-Mail: knoll@edv-design.at Internet: www.edv-design.at =20 Mit freundlichen Gr=FC=DFen Ing. Alfred Knoll Consulting & Projektmanagement=20 =20 EDV-Design Informationstechnologie GmbH Br=FCnner Stra=DFe 192/1/1, A-1210 Wien Tel: +43 1 29 22 165-50 Fax: +43 1 29 22 165-90 Mobil: +43 660 4614996 E-Mail: knoll@edv-design.at Internet: www.edv-design.at -------------------------------------------------------------------------= -------------------------------------------------------------------------= --------------- Hinweis: Dieses E-Mail kann vertrauliche und gesch=FCtzte Informationen = enthalten. Sollten Sie nicht der beabsichtigte Empf=E4nger sein, verst=E4ndigen Sie = bitte den Absender und l=F6schen Sie dieses E-Mail umgehend. Notice: This e-mail contains information that is confidential and may be = privileged. If you are not the intended recipient, please notify the sender and then = delete this e-mail immediately. -------------------------------------------------------------------------= -------------------------------------------------------------------------= ---------------=20 ###########################################=0A= =0A= This message has been scanned by F-Secure Anti-Virus for Microsoft = Exchange.=0A= For more information, connect to http://www.f-secure.com/ ------_=_NextPart_001_01C64C11.E455DC28-- From owner-freebsd-fs@FreeBSD.ORG Mon Mar 20 19:18:27 2006 Return-Path: X-Original-To: fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D45116A41F for ; Mon, 20 Mar 2006 19:18:27 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 845E943D4C for ; Mon, 20 Mar 2006 19:18:26 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 944F446BE9 for ; Mon, 20 Mar 2006 14:18:25 -0500 (EST) Date: Mon, 20 Mar 2006 19:18:25 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: fs@FreeBSD.org Message-ID: <20060320191736.K67379@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: RFC: Extended Attribute Support for tar (wd) 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, 20 Mar 2006 19:18:27 -0000 FYI. I'm sure Tim would appreciate comments from those actively using (or thinking about using) extended attributes and their backup semantics. Robert N M Watson ---------- Forwarded message ---------- Date: Sun, 19 Mar 2006 11:54:06 -0800 From: Tim Kientzle To: posix1e@freebsd.org Cc: Jaakko Heinonen Subject: RFC: Extended Attribute Support for tar To the members of the POSIX.1e mailing list: Jaakko Heinonen and I have developed the following approach for storing extended attributes in "pax extended format" (an extension of tar format) archives. This is implemented in libarchive-1.2.51 on : Background: pax extended format supports a general key/value mechanism in which keys and values are stored as UTF8 strings separated by an '=' character. Proposal: POSIX-style extended attributes are stored as separate pax attributes as follows: The pax name is LIBARCHIVE.xattr.. (Rationale: pax standard requires non-standard extensions be prefixed with an all-uppercase vendor name.) The extended attribute name (including namespace) is encoded using URL-encoding (specifically, '%' becomes '%25', '=' becomes '%3D', and all non-ASCII characters are similarly encoded). (Rationale: The encoding here avoids any problems from '=' characters appearing in the extended attribute name.) Note that the result of URL-encoding will be ASCII and hence already UTF-8. (Note: ASCII names that do not contain '%' or '=' appear in the archive exactly as they appear in the filesystem.) The value is base64 encoded (MIME encoding, except without line breaks and the last group is not padded). (Rationale: extended attribute values are binary and must not be modified; base64 encoding is widely understood.) By default, "system" and "root" namespaces are not archived. (Rationale: These are often not accessible to regular users. They are often used for ACLs and other properties that should be archived using other mechanisms.) Comparison with other approaches: Joerg Shilling's "star" implementation is the only "tar" program that I know of that attempts to archive extended attributes. It uses an approach similar to the above, but it does not encode the attribute name (hence cannot handle attributes with '=' or non-ASCII bytes in the name) and stores the attribute value as raw binary (which contradicts the pax specification which requires UTF8). Any comments or feedback are greatly appreciated. Tim Kientzle mailto:kientzle@freebsd.org _______________________________________________ posix1e@FreeBSD.org mailing list http://lists.freebsd.org/mailman/listinfo/posix1e To unsubscribe, send any mail to "posix1e-unsubscribe@FreeBSD.org" From owner-freebsd-fs@FreeBSD.ORG Tue Mar 21 01:45:03 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ADBF016A401; Tue, 21 Mar 2006 01:45:03 +0000 (UTC) (envelope-from saturnero@freesbie.org) Received: from jail1-fbsd4.consiagnet.it (jail1-fbsd4.consiagnet.it [83.149.128.151]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF49C43D4C; Tue, 21 Mar 2006 01:44:59 +0000 (GMT) (envelope-from saturnero@freesbie.org) Received: from jail1-fbsd4.consiagnet.it (jail1-fbsd4.consiagnet.it [83.149.128.151]) by jail1-fbsd4.consiagnet.it (Postfix) with ESMTP id 005C95797; Tue, 21 Mar 2006 02:55:10 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on cvs.freesbie.org X-Spam-Level: X-Spam-Status: No, score=0.6 required=5.0 tests=AWL,BAYES_00, RCVD_IN_NJABL_DUL,RCVD_IN_SORBS_DUL autolearn=no version=3.1.0 Received: from [192.168.99.16] (host129-150.pool875.interbusiness.it [87.5.150.129]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by jail1-fbsd4.consiagnet.it (Postfix) with ESMTP; Tue, 21 Mar 2006 02:55:10 +0100 (CET) Message-ID: <441F5A8E.5090404@freesbie.org> Date: Tue, 21 Mar 2006 02:44:46 +0100 From: Dario Freni User-Agent: Mozilla Thunderbird 1.5 (Macintosh/20051201) MIME-Version: 1.0 To: Jacques Marneweck References: <441A819A.5070100@powertrip.co.za> In-Reply-To: <441A819A.5070100@powertrip.co.za> X-Enigmail-Version: 0.94.0.0 OpenPGP: url=http://www.saturnero.net/saturnero.asc Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig755C5C081DE88858182F5ADC" X-Virus-Scanned: ClamAV using ClamSMTP Cc: ozawa@ongs.co.jp, freebsd-hackers@freebsd.org, 'Daichi GOTO' , freebsd-fs@freebsd.org, freebsd-current@freebsd.org, "'Mars G. Miro'" , Danny Braniss Subject: Re: patchset-9 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010) 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, 21 Mar 2006 01:45:04 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig755C5C081DE88858182F5ADC Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Jacques Marneweck ha scritto: > Danny Braniss wrote: >>> Daichi GOTO wrote: >>> =20 >>>> All folks have interests in improved unionfs should keep attentions >>>> and ask "how about merge?" at every turn :) >>>> =20 >>> OK. How about a merge? >>> >>> I'd really like to see this in 6-STABLE. >>> >>> Regards, >>> >>> Jan Mikkelsen. >>> =20 >> just a 'me too'. I've been running with the patch(under 6.1) and it's = >> definitely >> better than the panics with the unpatched version. in other words, >> IMHO, it does not break anything, and it actualy fixes somethings. >> >> danny >> =20 > Any ETA to when we can see this merged into 6.1 and 5.5? This patchset doesn't apply in 5.x branch. The unionfs code of 5.x is different and afaik is working quite well (we used it on freesbie 1.1 without problems). Cheers, --=20 Dario Freni (saturnero@freesbie.org) FreeSBIE developer (http://www.freesbie.org) GPG Public key at http://www.saturnero.net/saturnero.asc --------------enig755C5C081DE88858182F5ADC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEH1qTymi72IiShysRAsSDAJ41SGjn2b5HTmkJzN8AG3xX2zma5gCdFQA3 61JS++GZasR5BnkZm+1TwJI= =Dlnv -----END PGP SIGNATURE----- --------------enig755C5C081DE88858182F5ADC-- From owner-freebsd-fs@FreeBSD.ORG Tue Mar 21 09:36:55 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 862B016A422; Tue, 21 Mar 2006 09:36:55 +0000 (UTC) (envelope-from john@kozubik.com) Received: from kozubik.com (kozubik.com [69.43.165.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id EACD643D58; Tue, 21 Mar 2006 09:36:54 +0000 (GMT) (envelope-from john@kozubik.com) Received: from kozubik.com (localhost [127.0.0.1]) by kozubik.com (8.12.11/8.12.11) with ESMTP id k2L9ajgS022907; Tue, 21 Mar 2006 01:36:45 -0800 (PST) (envelope-from john@kozubik.com) Received: from localhost (john@localhost) by kozubik.com (8.12.11/8.12.11/Submit) with ESMTP id k2L9aiFL022904; Tue, 21 Mar 2006 01:36:44 -0800 (PST) (envelope-from john@kozubik.com) Date: Tue, 21 Mar 2006 01:36:44 -0800 (PST) From: John Kozubik To: freebsd-current@freebsd.org Message-ID: <20060320224313.O55763@kozubik.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-fs@freebsd.org, jroberson@chesapeake.net, tegge@freebsd.org, kris@obsecurity.org Subject: UFS2 Snapshots in 6.1-Beta4 - Confirmed Problems 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, 21 Mar 2006 09:36:55 -0000 Hello, By request of the participants of freebsd-fs, I have been testing the behavior and stability of UFS2 snapshots on FreeBSD 6.1-Beta4 for several days now. Unfortunately, I have confirmed that behavior from existing PRs (circa 6.0) still manifests itself, as well as some additional bad behavior that has not yet been documented in PRs. I hope that I am making this information available soon enough so that it may be acted upon prior to the release of 6.1. It would make me very happy to confidently use snapshots on FreeBSD (something that has never been possible in the past). ----- Here is the behavior I have witnessed: First, I have confirmed that a filesystem with multiple snapshots that undergoes multiple, rapid deletions of files, will cause the system to hang. I have witnessed this before, but had not confirmed it or documented it in a PR. Now that I have confirmed this behavior, I have documented it in: kern/94769 This is a serious problem because, in addition to making it nearly impossible to run a system with multiple snapshots, it is conceivable that enough rapid file deletions could occur on an otherwise non snapshotted system that has a single snapshot on it due to a background fsck, to cause the system to hang. Second, kern/92292 is still a problem. I have reproduced this error in 6.1-BETA4 (and have seen it happening since 5.1). The (small) difference is that the cp process seems to stick in the flswai state instead of biowr. This next one is complicated, and I haven't submitted a PR for it yet, but I believe it is quite serious for reasons I will expand on below. The problem is: If you completely fill a filesystem (109% usage in `df` on most systems) that has a snapshot on it, the system becomes very unresponsive - all interactive and disk response lags terribly and, although the system is not hung, it is in many cases unusable. I believe this is serious because it is conceivable that the snapshots on a filesystem contain critical data, while at the same time the system they are on is a critical system. If one allows a snapshotted filesystem to fill, one is faced with the difficult choice of deleting a snapshot with potentially critical data on it, or sacrificing the use of that _entire computer system_. Data cannot be deleted from that filesystem to free up space because that data continues to reside on the snapshots. This behavior makes it imperative that an administrator never allow a snapshotted filesystem to become full or close to full, which is perhaps unreasonable. Related to the last problem, is the fact that a filesystem (without snapshots) that is completely full will still sync properly with no errors. However, when one fills up a filesystem that already has snapshots living on it, sync fails with the message: /mnt/data1: write failed, filesystem is full I do not know if the sync is in fact unsuccessful or not. In essence, the current behavior means that a filesystem that has snapshots on it experiences a point of no return if that file system ever fills up completely. A snapshot _must be deleted_ to allow the system to return to reasonable performance. I have not been able to determine if kern/92272 still exists on FreeBSD 6.1BETA4. It looks like it does, but I haven't had time to test conclusively. Finally, most trivial, an attempted snapshot that fails due to insufficient space on the target filesystem fails with error: mksnap_ffs: Cannot create /mnt/data1/.snap/almost_full: No space left on device However, it still creates a zero byte file. I think it should create no file at all. Thank you for reviewing this - please contact me if there are further tests that I can run, or additional details I can provide. P.S. The items above related to bad behavior when disks fill are items I am having a hard time recreating perfectly. That is to say, every time I combine snapshots with full disks on 6.1-BETA4, bad things happen (terrible performance or hangs, or both), but I am having trouble recreating exact scenarios. YMMV. ----- John Kozubik - john@kozubik.com - http://www.kozubik.com From owner-freebsd-fs@FreeBSD.ORG Tue Mar 21 15:12:55 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6690516A401 for ; Tue, 21 Mar 2006 15:12:55 +0000 (UTC) (envelope-from jema@sendmail.ru) Received: from mail.agtel.net (babylon.agtel.net [212.111.64.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id C5CBB43D46 for ; Tue, 21 Mar 2006 15:12:54 +0000 (GMT) (envelope-from jema@sendmail.ru) Received: from [193.26.135.2] (account jema@sendmail.ru) by mail.agtel.net (CommuniGate Pro WebUser 4.2.8) with HTTP id 72539405 for freebsd-fs@freebsd.org; Tue, 21 Mar 2006 18:12:43 +0300 From: "Andy Jema" To: freebsd-fs@freebsd.org X-Mailer: CommuniGate Pro WebUser Interface v.4.2.8 Date: Tue, 21 Mar 2006 18:12:43 +0300 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="KOI8-R"; format="flowed" Content-Transfer-Encoding: 8bit Subject: UFS journalling status 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, 21 Mar 2006 15:12:55 -0000 Hello, fs hackers! Just wondering what's the current status of UFSJ project. Are there any substantial achievements available for alpha/beta testing? Sincerely yours, Andy From owner-freebsd-fs@FreeBSD.ORG Tue Mar 21 16:26:46 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F70216A422 for ; Tue, 21 Mar 2006 16:26:46 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCB0A43D46 for ; Tue, 21 Mar 2006 16:26:45 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k2LGQiUE026485; Tue, 21 Mar 2006 09:26:44 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <44202943.4080407@samsco.org> Date: Tue, 21 Mar 2006 09:26:43 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051230 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andy Jema References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-fs@freebsd.org Subject: Re: UFS journalling status 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, 21 Mar 2006 16:26:46 -0000 Andy Jema wrote: > Hello, fs hackers! > > Just wondering what's the current status of UFSJ project. > Are there any substantial achievements available for alpha/beta testing? > I'm going to be restarting the UFSJ work in a week or two as part of my daytime job. I hope to have something available for public testing within a few weeks of that. Scott From owner-freebsd-fs@FreeBSD.ORG Tue Mar 21 18:26:54 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B2FF16A422 for ; Tue, 21 Mar 2006 18:26:54 +0000 (UTC) (envelope-from mday@apple.com) Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44A4843D46 for ; Tue, 21 Mar 2006 18:26:53 +0000 (GMT) (envelope-from mday@apple.com) Received: from relay6.apple.com (a17-128-113-36.apple.com [17.128.113.36]) by mail-out3.apple.com (8.12.11/8.12.11) with ESMTP id k2LIQrx2008866 for ; Tue, 21 Mar 2006 10:26:53 -0800 (PST) Received: from [17.202.43.217] (doomsday.apple.com [17.202.43.217]) by relay6.apple.com (Apple SCV relay) with ESMTP id C052B1DB for ; Tue, 21 Mar 2006 10:26:53 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v749.3) In-Reply-To: References: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <3A96811D-55A9-4BA4-AF2D-2CBE6667BE2E@apple.com> Content-Transfer-Encoding: 7bit From: Mark Day Date: Tue, 21 Mar 2006 10:26:30 -0800 To: freebsd-fs@freebsd.org X-Mailer: Apple Mail (2.749.3) X-Brightmail-Tracker: AAAAAA== Subject: Re: Add a file flag for "hidden" files? 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, 21 Mar 2006 18:26:54 -0000 On Mar 1, 2006, at 9:48 AM, Mark Day wrote: > I could certainly provide patches to FreeBSD for the headers, FAT, > NTFS, and probably HFS. The strtofflags(3) and fflagstostr(3) > functions should also change so you can get at the flag bit via ls > (1), find(1), chflags(1), etc.; I think I could provide that patch, > too. (I've never actually used FreeBSD, so it will take me a bit > of time to get it installed, find my way around the sources, make > and test the changes.) FYI, I submitted a patch for , msdosfs, ntfs, and libc as kern/94519. Yar Tikhiy's HFS web page says that project is on hold, so I haven't made any patches for HFS. If there is interest in such a patch, just let me know. -Mark From owner-freebsd-fs@FreeBSD.ORG Tue Mar 21 18:41:29 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0300816A41F; Tue, 21 Mar 2006 18:41:29 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7042543D49; Tue, 21 Mar 2006 18:41:28 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 5960F1A4DCD; Tue, 21 Mar 2006 10:41:28 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id BF7F651FCA; Tue, 21 Mar 2006 13:41:27 -0500 (EST) Date: Tue, 21 Mar 2006 13:41:27 -0500 From: Kris Kennaway To: John Kozubik Message-ID: <20060321184127.GA19204@xor.obsecurity.org> References: <20060320224313.O55763@kozubik.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="J2SCkAp4GZ/dPZZf" Content-Disposition: inline In-Reply-To: <20060320224313.O55763@kozubik.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-fs@freebsd.org, jroberson@chesapeake.net, freebsd-current@freebsd.org, tegge@freebsd.org, kris@obsecurity.org Subject: Re: UFS2 Snapshots in 6.1-Beta4 - Confirmed Problems 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, 21 Mar 2006 18:41:29 -0000 --J2SCkAp4GZ/dPZZf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 21, 2006 at 01:36:44AM -0800, John Kozubik wrote: > Here is the behavior I have witnessed: >=20 >=20 > First, I have confirmed that a filesystem with multiple snapshots that > undergoes multiple, rapid deletions of files, will cause the system to > hang. I have witnessed this before, but had not confirmed it or > documented it in a PR. Now that I have confirmed this behavior, I have > documented it in: kern/94769 >=20 > This is a serious problem because, in addition to making it nearly > impossible to run a system with multiple snapshots, it is conceivable that > enough rapid file deletions could occur on an otherwise non snapshotted > system that has a single snapshot on it due to a background fsck, to cause > the system to hang. > Second, kern/92292 is still a problem. I have reproduced this error in > 6.1-BETA4 (and have seen it happening since 5.1). The (small) difference > is that the cp process seems to stick in the flswai state instead of > biowr. Thanks, I'll try to reproduce these two. > This next one is complicated, and I haven't submitted a PR for it yet, but > I believe it is quite serious for reasons I will expand on below. >=20 > The problem is: If you completely fill a filesystem (109% usage in `df` > on most systems) that has a snapshot on it, the system becomes very > unresponsive - all interactive and disk response lags terribly and, > although the system is not hung, it is in many cases unusable. Yes :-( This will probably not be fixable in time for 6.1, but hopefully it will be addressed in the future. FYI, the system may also panic in this situation. Kris --J2SCkAp4GZ/dPZZf Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEIEjWWry0BWjoQKURAhsiAJ9hM3S6oc9mSZmlT+/ArqJIrv8oGgCgsDkQ 5Vh0MycEjF/FC8O7VT9IXL8= =RopU -----END PGP SIGNATURE----- --J2SCkAp4GZ/dPZZf-- From owner-freebsd-fs@FreeBSD.ORG Tue Mar 21 19:40:51 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC15616A41F; Tue, 21 Mar 2006 19:40:51 +0000 (UTC) (envelope-from john@kozubik.com) Received: from kozubik.com (kozubik.com [69.43.165.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9525343D45; Tue, 21 Mar 2006 19:40:51 +0000 (GMT) (envelope-from john@kozubik.com) Received: from kozubik.com (localhost [127.0.0.1]) by kozubik.com (8.12.11/8.12.11) with ESMTP id k2LJeiUZ034086; Tue, 21 Mar 2006 11:40:44 -0800 (PST) (envelope-from john@kozubik.com) Received: from localhost (john@localhost) by kozubik.com (8.12.11/8.12.11/Submit) with ESMTP id k2LJeig8034083; Tue, 21 Mar 2006 11:40:44 -0800 (PST) (envelope-from john@kozubik.com) Date: Tue, 21 Mar 2006 11:40:44 -0800 (PST) From: John Kozubik To: Kris Kennaway In-Reply-To: <20060321184127.GA19204@xor.obsecurity.org> Message-ID: <20060321113923.I55763@kozubik.com> References: <20060320224313.O55763@kozubik.com> <20060321184127.GA19204@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-fs@freebsd.org, jroberson@chesapeake.net, freebsd-current@freebsd.org, tegge@freebsd.org Subject: Re: UFS2 Snapshots in 6.1-Beta4 - Confirmed Problems 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, 21 Mar 2006 19:40:52 -0000 On Tue, 21 Mar 2006, Kris Kennaway wrote: > > This next one is complicated, and I haven't submitted a PR for it yet, but > > I believe it is quite serious for reasons I will expand on below. > > > > The problem is: If you completely fill a filesystem (109% usage in `df` > > on most systems) that has a snapshot on it, the system becomes very > > unresponsive - all interactive and disk response lags terribly and, > > although the system is not hung, it is in many cases unusable. > > Yes :-( This will probably not be fixable in time for 6.1, but > hopefully it will be addressed in the future. FYI, the system may > also panic in this situation. Because my original description of this behavior was so vague, I was going to try to reproduce it again with more details, however it sounds like you have already witnessed this and know more about it than I do. Is that true ? Can I skip a few hours of trying to reproduce this ? ----- John Kozubik - john@kozubik.com - http://www.kozubik.com From owner-freebsd-fs@FreeBSD.ORG Tue Mar 21 19:49:05 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7CD616A420; Tue, 21 Mar 2006 19:49:05 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01AC943D5C; Tue, 21 Mar 2006 19:49:05 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id DF2421A4DD1; Tue, 21 Mar 2006 11:49:04 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 539FF515BE; Tue, 21 Mar 2006 14:49:04 -0500 (EST) Date: Tue, 21 Mar 2006 14:49:04 -0500 From: Kris Kennaway To: John Kozubik Message-ID: <20060321194904.GA20959@xor.obsecurity.org> References: <20060320224313.O55763@kozubik.com> <20060321184127.GA19204@xor.obsecurity.org> <20060321113923.I55763@kozubik.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cWoXeonUoKmBZSoM" Content-Disposition: inline In-Reply-To: <20060321113923.I55763@kozubik.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-fs@freebsd.org, jroberson@chesapeake.net, freebsd-current@freebsd.org, tegge@freebsd.org, Kris Kennaway Subject: Re: UFS2 Snapshots in 6.1-Beta4 - Confirmed Problems 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, 21 Mar 2006 19:49:05 -0000 --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 21, 2006 at 11:40:44AM -0800, John Kozubik wrote: >=20 >=20 > On Tue, 21 Mar 2006, Kris Kennaway wrote: >=20 > > > This next one is complicated, and I haven't submitted a PR for it yet= , but > > > I believe it is quite serious for reasons I will expand on below. > > > > > > The problem is: If you completely fill a filesystem (109% usage in `= df` > > > on most systems) that has a snapshot on it, the system becomes very > > > unresponsive - all interactive and disk response lags terribly and, > > > although the system is not hung, it is in many cases unusable. > > > > Yes :-( This will probably not be fixable in time for 6.1, but > > hopefully it will be addressed in the future. FYI, the system may > > also panic in this situation. >=20 >=20 > Because my original description of this behavior was so vague, I was going > to try to reproduce it again with more details, however it sounds like you > have already witnessed this and know more about it than I do. >=20 > Is that true ? Can I skip a few hours of trying to reproduce this ? Yes, I'm easily able to reproduce it, and I'm told that fixing it will require fairly extensive work & testing. Kris --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEIFivWry0BWjoQKURAhtMAKCPf9EejvGpZ1a3nl2ou2dkEQCeKgCgzswY zBBpyed8lGzCvRrzD0aDltg= =fHvo -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM-- From owner-freebsd-fs@FreeBSD.ORG Tue Mar 21 20:07:12 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B8CB16A400; Tue, 21 Mar 2006 20:07:12 +0000 (UTC) (envelope-from john@kozubik.com) Received: from kozubik.com (kozubik.com [69.43.165.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id D67D143D48; Tue, 21 Mar 2006 20:07:11 +0000 (GMT) (envelope-from john@kozubik.com) Received: from kozubik.com (localhost [127.0.0.1]) by kozubik.com (8.12.11/8.12.11) with ESMTP id k2LK74Om034435; Tue, 21 Mar 2006 12:07:04 -0800 (PST) (envelope-from john@kozubik.com) Received: from localhost (john@localhost) by kozubik.com (8.12.11/8.12.11/Submit) with ESMTP id k2LK74uq034432; Tue, 21 Mar 2006 12:07:04 -0800 (PST) (envelope-from john@kozubik.com) Date: Tue, 21 Mar 2006 12:07:04 -0800 (PST) From: John Kozubik To: Kris Kennaway In-Reply-To: <20060321194904.GA20959@xor.obsecurity.org> Message-ID: <20060321120255.I55763@kozubik.com> References: <20060320224313.O55763@kozubik.com> <20060321184127.GA19204@xor.obsecurity.org> <20060321113923.I55763@kozubik.com> <20060321194904.GA20959@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-fs@freebsd.org, jroberson@chesapeake.net, tegge@freebsd.org Subject: Re: UFS2 Snapshots in 6.1-Beta4 - Confirmed Problems 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, 21 Mar 2006 20:07:12 -0000 On Tue, 21 Mar 2006, Kris Kennaway wrote: > > > > This next one is complicated, and I haven't submitted a PR for it yet, but > > > > I believe it is quite serious for reasons I will expand on below. > > > > > > > > The problem is: If you completely fill a filesystem (109% usage in `df` > > > > on most systems) that has a snapshot on it, the system becomes very > > > > unresponsive - all interactive and disk response lags terribly and, > > > > although the system is not hung, it is in many cases unusable. > > > > > > Yes :-( This will probably not be fixable in time for 6.1, but > > > hopefully it will be addressed in the future. FYI, the system may > > > also panic in this situation. > > > > > > Because my original description of this behavior was so vague, I was going > > to try to reproduce it again with more details, however it sounds like you > > have already witnessed this and know more about it than I do. > > > > Is that true ? Can I skip a few hours of trying to reproduce this ? > > Yes, I'm easily able to reproduce it, and I'm told that fixing it will > require fairly extensive work & testing. Ok. Please contact me when that testing is needed as I am happy to help. Can I use this time to suggest that in all testing of snapshot related issues, that multiple (preferably 4+) snapshots per filesystem are used ? Many of the problems either do not manifest themselves, or are not as pronounced with only one snapshot running. Thanks. ----- John Kozubik - john@kozubik.com - http://www.kozubik.com From owner-freebsd-fs@FreeBSD.ORG Tue Mar 21 20:45:17 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76D0916A424; Tue, 21 Mar 2006 20:45:17 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2802D43D45; Tue, 21 Mar 2006 20:45:17 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 0B0521A4DD1; Tue, 21 Mar 2006 12:45:17 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 58CF6523B5; Tue, 21 Mar 2006 15:45:16 -0500 (EST) Date: Tue, 21 Mar 2006 15:45:16 -0500 From: Kris Kennaway To: John Kozubik Message-ID: <20060321204516.GA21989@xor.obsecurity.org> References: <20060320224313.O55763@kozubik.com> <20060321184127.GA19204@xor.obsecurity.org> <20060321113923.I55763@kozubik.com> <20060321194904.GA20959@xor.obsecurity.org> <20060321120255.I55763@kozubik.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IS0zKkzwUGydFO0o" Content-Disposition: inline In-Reply-To: <20060321120255.I55763@kozubik.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-fs@freebsd.org, jroberson@chesapeake.net, tegge@freebsd.org, Kris Kennaway Subject: Re: UFS2 Snapshots in 6.1-Beta4 - Confirmed Problems 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, 21 Mar 2006 20:45:17 -0000 --IS0zKkzwUGydFO0o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 21, 2006 at 12:07:04PM -0800, John Kozubik wrote: >=20 >=20 > On Tue, 21 Mar 2006, Kris Kennaway wrote: >=20 > > > > > This next one is complicated, and I haven't submitted a PR for it= yet, but > > > > > I believe it is quite serious for reasons I will expand on below. > > > > > > > > > > The problem is: If you completely fill a filesystem (109% usage = in `df` > > > > > on most systems) that has a snapshot on it, the system becomes ve= ry > > > > > unresponsive - all interactive and disk response lags terribly an= d, > > > > > although the system is not hung, it is in many cases unusable. > > > > > > > > Yes :-( This will probably not be fixable in time for 6.1, but > > > > hopefully it will be addressed in the future. FYI, the system may > > > > also panic in this situation. > > > > > > > > > Because my original description of this behavior was so vague, I was = going > > > to try to reproduce it again with more details, however it sounds lik= e you > > > have already witnessed this and know more about it than I do. > > > > > > Is that true ? Can I skip a few hours of trying to reproduce this ? > > > > Yes, I'm easily able to reproduce it, and I'm told that fixing it will > > require fairly extensive work & testing. >=20 >=20 > Ok. Please contact me when that testing is needed as I am happy to help. >=20 > Can I use this time to suggest that in all testing of snapshot related > issues, that multiple (preferably 4+) snapshots per filesystem are used ? > Many of the problems either do not manifest themselves, or are not as > pronounced with only one snapshot running. Yeah, I usually use 20 ;-) Kris --IS0zKkzwUGydFO0o Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEIGXbWry0BWjoQKURAjX0AKCl4EAAqS6EE/JZVVdgKkDhL/CuywCffJQv XGe4rkl8R6cEkso7BSQ1j+Y= =rB17 -----END PGP SIGNATURE----- --IS0zKkzwUGydFO0o-- From owner-freebsd-fs@FreeBSD.ORG Wed Mar 22 13:57:00 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2862D16A400 for ; Wed, 22 Mar 2006 13:57:00 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C51D443D4C for ; Wed, 22 Mar 2006 13:56:59 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k2MDur4j062648; Wed, 22 Mar 2006 07:56:55 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <442157A1.6060508@centtech.com> Date: Wed, 22 Mar 2006 07:56:49 -0600 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060112) MIME-Version: 1.0 To: Mark Day References: <3A96811D-55A9-4BA4-AF2D-2CBE6667BE2E@apple.com> In-Reply-To: <3A96811D-55A9-4BA4-AF2D-2CBE6667BE2E@apple.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1350/Wed Mar 22 04:12:47 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-fs@freebsd.org Subject: Re: Add a file flag for "hidden" files? 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, 22 Mar 2006 13:57:00 -0000 Mark Day wrote: > On Mar 1, 2006, at 9:48 AM, Mark Day wrote: > >> I could certainly provide patches to FreeBSD for the headers, FAT, >> NTFS, and probably HFS. The strtofflags(3) and fflagstostr(3) >> functions should also change so you can get at the flag bit via >> ls(1), find(1), chflags(1), etc.; I think I could provide that patch, >> too. (I've never actually used FreeBSD, so it will take me a bit of >> time to get it installed, find my way around the sources, make and >> test the changes.) > > FYI, I submitted a patch for , msdosfs, ntfs, and libc as > kern/94519. > > Yar Tikhiy's HFS web page says that project is on hold, so I haven't > made any patches for HFS. If there is interest in such a patch, just > let me know. The patch applies clean on 6.1-BETA4, and seems to work as expected. Thanks for the patch! I got about half way through implementing the same thing, and for some reason, I chose SF_HIDDEN instead of UF_HIDDEN, where UF_HIDDEN makes more sense really. I have one question (for anyone) - in what function or syscall would we intercept directory listings (opendir?) to ignore files/directories with this bit set? The reason I'm asking, is I'd like to mark directories containing snapshots as hidden & snapshot, and have the system not traverse those directories while a snapshot is being taken, to avoid blocking on locks when a snapshot is being created. Thanks again for the work, Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-fs@FreeBSD.ORG Thu Mar 23 09:28:59 2006 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 52B4E16A420 for ; Thu, 23 Mar 2006 09:28:59 +0000 (UTC) (envelope-from Nicolas.Kowalski@imag.fr) Received: from imag.imag.fr (imag.imag.fr [129.88.30.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69C5B43D46 for ; Thu, 23 Mar 2006 09:28:58 +0000 (GMT) (envelope-from Nicolas.Kowalski@imag.fr) Received: from mail-veri.imag.fr (mail-veri.imag.fr [129.88.43.52]) by imag.imag.fr (8.13.0/8.13.0) with ESMTP id k2N9Ss8x021661 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Thu, 23 Mar 2006 10:28:54 +0100 (CET) Received: from corbeau.imag.fr ([129.88.43.162]) by mail-veri.imag.fr with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1FMM7i-0000DA-17 for freebsd-fs@FreeBSD.org; Thu, 23 Mar 2006 10:28:54 +0100 Received: from kowalski by corbeau.imag.fr with local (Exim 4.50) id 1FMM7h-0003DW-EO for freebsd-fs@FreeBSD.org; Thu, 23 Mar 2006 10:28:53 +0100 To: freebsd-fs@FreeBSD.org From: Nicolas KOWALSKI Date: Thu, 23 Mar 2006 10:28:53 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: Nicolas Kowalski X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.6 (imag.imag.fr [129.88.30.1]); Thu, 23 Mar 2006 10:28:54 +0100 (CET) X-IMAG-MailScanner: Found to be clean X-IMAG-MailScanner-Information: Please contact the ISP for more information Cc: Subject: quotas problem on 4.11/UFS 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, 23 Mar 2006 09:28:59 -0000 Hello, Our FreeBSD 4.11 fileserver (NFS, Samba) seems to have some problems with quotas, apparently just after a lot of files are deleted. The clients are mostly Linux 2.6 workstations (75), and some Windows XP (10). For example, yesterday the quota files of one disk were these: -rw-r----- 1 root tty 2097120 Mar 21 23:14 quota.group -rw-r----- 1 root tty 2097120 Mar 21 23:14 quota.user But today, after a user deleted a lot of his files, the quotas files are: -rw-r----- 1 root tty 2097120 Mar 22 23:10 quota.group -rw-r----- 1 root tty 4294967264 Mar 22 23:10 quota.user The repquota command still works, but takes more time (30 secs instead of immediate). We will reboot the server today to rebuild the quota files. Does anyone know what is happenning here, and if possible how to prevent it ? Thanks. PS: some informations... pave# uname -a FreeBSD pave.imag.fr 4.11-RELEASE-p13 FreeBSD 4.11-RELEASE-p13 #5: Mon Oct 17 11:49:43 CEST 2005 root@pave.imag.fr:/usr/obj/usr/src/sys/PAVE i386 pave# mount /dev/da0s1a on / (ufs, local) /dev/da0s1e on /var (ufs, local, soft-updates) /dev/da0s1f on /tmp (ufs, local, soft-updates) /dev/da0s1g on /usr (ufs, local, soft-updates) /dev/da1s1e on /export/local (ufs, NFS exported, local, with quotas, soft-updates) /dev/da2s1e on /export/home (ufs, NFS exported, local, with quotas, soft-updates) /dev/da3s1e on /export/home2 (ufs, NFS exported, local, with quotas, soft-updates) pave# df /export/home2 Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da3s1e 70566166 41328314 23592560 64% /export/home2 pave# df -i /export/home2 Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/da3s1e 70566166 41346828 23574046 64% 944519 7881079 11% /export/home2 -- Nicolas From owner-freebsd-fs@FreeBSD.ORG Thu Mar 23 18:34:19 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 629D716A424; Thu, 23 Mar 2006 18:34:19 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40AAE43DC0; Thu, 23 Mar 2006 18:34:15 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id D4D241A4E87; Thu, 23 Mar 2006 10:34:14 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 365AB51753; Thu, 23 Mar 2006 13:34:14 -0500 (EST) Date: Thu, 23 Mar 2006 13:34:14 -0500 From: Kris Kennaway To: John Kozubik Message-ID: <20060323183414.GA84775@xor.obsecurity.org> References: <20060320224313.O55763@kozubik.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="45Z9DzgjV8m4Oswq" Content-Disposition: inline In-Reply-To: <20060320224313.O55763@kozubik.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-fs@freebsd.org, jroberson@chesapeake.net, freebsd-current@freebsd.org, tegge@freebsd.org, kris@obsecurity.org Subject: Re: UFS2 Snapshots in 6.1-Beta4 - Confirmed Problems 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, 23 Mar 2006 18:34:19 -0000 --45Z9DzgjV8m4Oswq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Mar 21, 2006 at 01:36:44AM -0800, John Kozubik wrote: > First, I have confirmed that a filesystem with multiple snapshots that > undergoes multiple, rapid deletions of files, will cause the system to > hang. I have witnessed this before, but had not confirmed it or > documented it in a PR. Now that I have confirmed this behavior, I have > documented it in: kern/94769 I ran a (completion of) your script in a loop for about 24 hours and it didn't deadlock. This may be because there was a second set of fixes that was merged in to 6.x a day or two ago. Are you able to confirm whether they indeed fixed this problem? > Second, kern/92292 is still a problem. I have reproduced this error in > 6.1-BETA4 (and have seen it happening since 5.1). The (small) difference > is that the cp process seems to stick in the flswai state instead of > biowr. I'll test this one next. Kris --45Z9DzgjV8m4Oswq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEIuolWry0BWjoQKURAk5hAJwNxVVgMARq2Vuxr7j+WEaBgckiHgCg7a3S oR0bG21GB9Mg1bNFYlHM96M= =EUji -----END PGP SIGNATURE----- --45Z9DzgjV8m4Oswq-- From owner-freebsd-fs@FreeBSD.ORG Thu Mar 23 18:42:44 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 64F2F16A422; Thu, 23 Mar 2006 18:42:44 +0000 (UTC) (envelope-from kstewart@owt.com) Received: from smtp.owt.com (smtp.owt.com [204.118.6.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id B840843D6A; Thu, 23 Mar 2006 18:42:42 +0000 (GMT) (envelope-from kstewart@owt.com) Received: from topaz-out (owt-207-41-94-233.owt.com [207.41.94.233]) by smtp.owt.com (8.12.8/8.12.8) with ESMTP id k2NIg91Z030001; Thu, 23 Mar 2006 10:42:09 -0800 From: Kent Stewart To: freebsd-current@freebsd.org Date: Thu, 23 Mar 2006 10:42:30 -0800 User-Agent: KMail/1.9.1 References: <20060320224313.O55763@kozubik.com> <20060323183414.GA84775@xor.obsecurity.org> In-Reply-To: <20060323183414.GA84775@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603231042.30623.kstewart@owt.com> Cc: freebsd-fs@freebsd.org, jroberson@chesapeake.net, tegge@freebsd.org, Kris Kennaway Subject: Re: UFS2 Snapshots in 6.1-Beta4 - Confirmed Problems 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, 23 Mar 2006 18:42:44 -0000 On Thursday 23 March 2006 10:34, Kris Kennaway wrote: > On Tue, Mar 21, 2006 at 01:36:44AM -0800, John Kozubik wrote: > > First, I have confirmed that a filesystem with multiple snapshots > > that undergoes multiple, rapid deletions of files, will cause the > > system to hang. I have witnessed this before, but had not > > confirmed it or documented it in a PR. Now that I have confirmed > > this behavior, I have documented it in: kern/94769 > > I ran a (completion of) your script in a loop for about 24 hours and > it didn't deadlock. This may be because there was a second set of > fixes that was merged in to 6.x a day or two ago. Are you able to > confirm whether they indeed fixed this problem? > > > Second, kern/92292 is still a problem. I have reproduced this > > error in 6.1-BETA4 (and have seen it happening since 5.1). The > > (small) difference is that the cp process seems to stick in the > > flswai state instead of biowr. > > I'll test this one next. There is also a problem if you try to boot the latest 6.1-beta kernel from XP using an old boot1. It just hangs and you don't even see the "-" symbol on the console. You can boot from XP after you start using the new boot1. Kent -- Kent Stewart Richland, WA http://www.soyandina.com/ "I am Andean project". http://users.owt.com/kstewart/index.html From owner-freebsd-fs@FreeBSD.ORG Thu Mar 23 18:43:08 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 177DE16A424; Thu, 23 Mar 2006 18:43:08 +0000 (UTC) (envelope-from john@kozubik.com) Received: from kozubik.com (kozubik.com [69.43.165.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8AD643D76; Thu, 23 Mar 2006 18:43:06 +0000 (GMT) (envelope-from john@kozubik.com) Received: from kozubik.com (localhost [127.0.0.1]) by kozubik.com (8.12.11/8.12.11) with ESMTP id k2NIh02w095019; Thu, 23 Mar 2006 10:43:00 -0800 (PST) (envelope-from john@kozubik.com) Received: from localhost (john@localhost) by kozubik.com (8.12.11/8.12.11/Submit) with ESMTP id k2NIgxn9095016; Thu, 23 Mar 2006 10:43:00 -0800 (PST) (envelope-from john@kozubik.com) Date: Thu, 23 Mar 2006 10:42:59 -0800 (PST) From: John Kozubik To: Kris Kennaway In-Reply-To: <20060323183414.GA84775@xor.obsecurity.org> Message-ID: <20060323103850.S55763@kozubik.com> References: <20060320224313.O55763@kozubik.com> <20060323183414.GA84775@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-fs@freebsd.org, jroberson@chesapeake.net, freebsd-current@freebsd.org, tegge@freebsd.org Subject: Re: UFS2 Snapshots in 6.1-Beta4 - Confirmed Problems 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, 23 Mar 2006 18:43:08 -0000 On Thu, 23 Mar 2006, Kris Kennaway wrote: > On Tue, Mar 21, 2006 at 01:36:44AM -0800, John Kozubik wrote: > > > First, I have confirmed that a filesystem with multiple snapshots that > > undergoes multiple, rapid deletions of files, will cause the system to > > hang. I have witnessed this before, but had not confirmed it or > > documented it in a PR. Now that I have confirmed this behavior, I have > > documented it in: kern/94769 > > I ran a (completion of) your script in a loop for about 24 hours and > it didn't deadlock. This may be because there was a second set of > fixes that was merged in to 6.x a day or two ago. Are you able to > confirm whether they indeed fixed this problem? What ratio of snapshots / rms did you run ? I reproduced this easily on 6.0-RELEASE and 6.1-BETA4. I am traveling right now and cannot test on anything newer. Can you try it on one of the two above, confirm for yourself that it manifests itself, and then compare that to what you see on whatever newer code you have ? If it is fixed, that's great. > > Second, kern/92292 is still a problem. I have reproduced this error in > > 6.1-BETA4 (and have seen it happening since 5.1). The (small) difference > > is that the cp process seems to stick in the flswai state instead of > > biowr. > > I'll test this one next. Great - thanks. It's less urgent, as running a md-backed FS on a snapshotted FS is less common, and easily avoided. The big fish are the rm problems (you can't avoid deleting things) and the "full filesystem" problems, since there is always a danger of that. ----- John Kozubik - john@kozubik.com - http://www.kozubik.com From owner-freebsd-fs@FreeBSD.ORG Thu Mar 23 18:47:42 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F1A316A422; Thu, 23 Mar 2006 18:47:42 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id DEABD43D60; Thu, 23 Mar 2006 18:47:41 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 97F651A3C1C; Thu, 23 Mar 2006 10:47:40 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 02E3151753; Thu, 23 Mar 2006 13:47:40 -0500 (EST) Date: Thu, 23 Mar 2006 13:47:39 -0500 From: Kris Kennaway To: Kent Stewart Message-ID: <20060323184739.GA85076@xor.obsecurity.org> References: <20060320224313.O55763@kozubik.com> <20060323183414.GA84775@xor.obsecurity.org> <200603231042.30623.kstewart@owt.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="azLHFNyN32YCQGCU" Content-Disposition: inline In-Reply-To: <200603231042.30623.kstewart@owt.com> User-Agent: Mutt/1.4.2.1i Cc: Kris Kennaway , freebsd-fs@freebsd.org, freebsd-current@freebsd.org, jroberson@chesapeake.net, tegge@freebsd.org Subject: Re: UFS2 Snapshots in 6.1-Beta4 - Confirmed Problems 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, 23 Mar 2006 18:47:42 -0000 --azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 23, 2006 at 10:42:30AM -0800, Kent Stewart wrote: > On Thursday 23 March 2006 10:34, Kris Kennaway wrote: > > On Tue, Mar 21, 2006 at 01:36:44AM -0800, John Kozubik wrote: > > > First, I have confirmed that a filesystem with multiple snapshots > > > that undergoes multiple, rapid deletions of files, will cause the > > > system to hang. I have witnessed this before, but had not > > > confirmed it or documented it in a PR. Now that I have confirmed > > > this behavior, I have documented it in: kern/94769 > > > > I ran a (completion of) your script in a loop for about 24 hours and > > it didn't deadlock. This may be because there was a second set of > > fixes that was merged in to 6.x a day or two ago. Are you able to > > confirm whether they indeed fixed this problem? > > > > > Second, kern/92292 is still a problem. I have reproduced this > > > error in 6.1-BETA4 (and have seen it happening since 5.1). The > > > (small) difference is that the cp process seems to stick in the > > > flswai state instead of biowr. > > > > I'll test this one next. >=20 > There is also a problem if you try to boot the latest 6.1-beta kernel=20 > from XP using an old boot1. It just hangs and you don't even see the=20 > "-" symbol on the console. You can boot from XP after you start using=20 > the new boot1. Sounds entirely unrelated to snapshots, so go find your own thread :-) Kris --azLHFNyN32YCQGCU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEIu1LWry0BWjoQKURAhxnAKDK+ybrKBnWEZoD0n+JK+AjzhTY8ACgiAEn E37x2hlfvsr/OEw8EIDyxqs= =8xpE -----END PGP SIGNATURE----- --azLHFNyN32YCQGCU-- From owner-freebsd-fs@FreeBSD.ORG Thu Mar 23 18:57:24 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D71716A41F; Thu, 23 Mar 2006 18:57:24 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id B922243D46; Thu, 23 Mar 2006 18:57:18 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 9CE5C1A4E87; Thu, 23 Mar 2006 10:57:18 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 175EE51753; Thu, 23 Mar 2006 13:57:18 -0500 (EST) Date: Thu, 23 Mar 2006 13:57:18 -0500 From: Kris Kennaway To: John Kozubik Message-ID: <20060323185717.GA85305@xor.obsecurity.org> References: <20060320224313.O55763@kozubik.com> <20060323183414.GA84775@xor.obsecurity.org> <20060323103850.S55763@kozubik.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="DocE+STaALJfprDB" Content-Disposition: inline In-Reply-To: <20060323103850.S55763@kozubik.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-fs@freebsd.org, jroberson@chesapeake.net, freebsd-current@freebsd.org, tegge@freebsd.org, Kris Kennaway Subject: Re: UFS2 Snapshots in 6.1-Beta4 - Confirmed Problems 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, 23 Mar 2006 18:57:24 -0000 --DocE+STaALJfprDB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 23, 2006 at 10:42:59AM -0800, John Kozubik wrote: >=20 >=20 > On Thu, 23 Mar 2006, Kris Kennaway wrote: >=20 > > On Tue, Mar 21, 2006 at 01:36:44AM -0800, John Kozubik wrote: > > > > > First, I have confirmed that a filesystem with multiple snapshots that > > > undergoes multiple, rapid deletions of files, will cause the system to > > > hang. I have witnessed this before, but had not confirmed it or > > > documented it in a PR. Now that I have confirmed this behavior, I ha= ve > > > documented it in: kern/94769 > > > > I ran a (completion of) your script in a loop for about 24 hours and > > it didn't deadlock. This may be because there was a second set of > > fixes that was merged in to 6.x a day or two ago. Are you able to > > confirm whether they indeed fixed this problem? >=20 > What ratio of snapshots / rms did you run ? 3/3, as you suggested. > I reproduced this easily on > 6.0-RELEASE and 6.1-BETA4. I am traveling right now and cannot test on > anything newer. Can you try it on one of the two above, confirm for > yourself that it manifests itself, and then compare that to what you see > on whatever newer code you have ? If it is fixed, that's great. Not right away, unfortunately. > > > Second, kern/92292 is still a problem. I have reproduced this error = in > > > 6.1-BETA4 (and have seen it happening since 5.1). The (small) differ= ence > > > is that the cp process seems to stick in the flswai state instead of > > > biowr. > > > > I'll test this one next. >=20 >=20 > Great - thanks. It's less urgent, as running a md-backed FS on a > snapshotted FS is less common, and easily avoided. The big fish are the > rm problems (you can't avoid deleting things) and the "full filesystem" > problems, since there is always a danger of that. Yeah, the full filesystem bugs are a big pain, but as I mentioned probably nothing can be done in time for 6.1 since it's a pretty big job. Kris --DocE+STaALJfprDB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEIu+NWry0BWjoQKURAgZBAKCEw63xQ5VBjrcnmlFOUvQjMAH94ACeOse5 E1NRLbQ7ONWK2xmbKvuaUjc= =j454 -----END PGP SIGNATURE----- --DocE+STaALJfprDB-- From owner-freebsd-fs@FreeBSD.ORG Thu Mar 23 19:07:51 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4ADF16A420; Thu, 23 Mar 2006 19:07:51 +0000 (UTC) (envelope-from john@kozubik.com) Received: from kozubik.com (kozubik.com [69.43.165.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69D4D43D6D; Thu, 23 Mar 2006 19:07:38 +0000 (GMT) (envelope-from john@kozubik.com) Received: from kozubik.com (localhost [127.0.0.1]) by kozubik.com (8.12.11/8.12.11) with ESMTP id k2NJ7WpB095304; Thu, 23 Mar 2006 11:07:32 -0800 (PST) (envelope-from john@kozubik.com) Received: from localhost (john@localhost) by kozubik.com (8.12.11/8.12.11/Submit) with ESMTP id k2NJ7WI7095301; Thu, 23 Mar 2006 11:07:32 -0800 (PST) (envelope-from john@kozubik.com) Date: Thu, 23 Mar 2006 11:07:32 -0800 (PST) From: John Kozubik To: Kris Kennaway In-Reply-To: <20060323185717.GA85305@xor.obsecurity.org> Message-ID: <20060323110458.W55763@kozubik.com> References: <20060320224313.O55763@kozubik.com> <20060323183414.GA84775@xor.obsecurity.org> <20060323103850.S55763@kozubik.com> <20060323185717.GA85305@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-fs@freebsd.org, jroberson@chesapeake.net, freebsd-current@freebsd.org, tegge@freebsd.org Subject: Re: UFS2 Snapshots in 6.1-Beta4 - Confirmed Problems 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, 23 Mar 2006 19:07:51 -0000 Kris, et al., On Thu, 23 Mar 2006, Kris Kennaway wrote: > > > I ran a (completion of) your script in a loop for about 24 hours and > > > it didn't deadlock. This may be because there was a second set of > > > fixes that was merged in to 6.x a day or two ago. Are you able to > > > confirm whether they indeed fixed this problem? > > > > What ratio of snapshots / rms did you run ? > > 3/3, as you suggested. Ok. If you have code that is newer than the 6.1-BETA4 ISO that I downloaded to do my tests with, then perhaps it is fixed. Could you try it one more time, though, with: 8 snapshots / 4 rms ? If it lives through that, doing big rms of source trees on the FS that is snapshotted (8 times), then I guess it is fixed. Thanks. ----- John Kozubik - john@kozubik.com - http://www.kozubik.com From owner-freebsd-fs@FreeBSD.ORG Thu Mar 23 20:34:53 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C75C316A420 for ; Thu, 23 Mar 2006 20:34:53 +0000 (UTC) (envelope-from genie@geniechka.ru) Received: from turists.ru (turists.ru [83.222.5.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id B31DA43D60 for ; Thu, 23 Mar 2006 20:34:47 +0000 (GMT) (envelope-from genie@geniechka.ru) Received: from genie (genie.yauza.ru [85.192.18.27]) (authenticated bits=0) by turists.ru (8.13.1/8.13.1) with ESMTP id k2NKYj8N037371; Thu, 23 Mar 2006 23:34:45 +0300 (MSK) (envelope-from genie@geniechka.ru) X-AntiVirus: Checked by Dr.Web [version: 4.33, engine: 4.33.2.02271, virus records: 107569, updated: 23.02.2006] Message-ID: <007801c64eb9$3db4c050$1b12c055@genie> From: "Eugene" To: References: <20060322120033.E5B8916A44B@hub.freebsd.org> Date: Thu, 23 Mar 2006 23:34:40 +0300 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Cc: Kris Kennaway Subject: Re: UFS2 Snapshots in 6.1-Beta4 - Confirmed Problems 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, 23 Mar 2006 20:34:53 -0000 Hi all! While we're on the topic of snapshots, I recently posted this follow-up to the PR kern/66270 "[hang] dump causes machine freeze" > I wonder what is the status of this PR? > I seem to have the same problem with 5.3-RELEASE. > > Before this started, system worked nicely for more than a year and then > it > started to hang during dump (seemingly just after mksnap_ffs) first > intermittently and now reproducibly (might increase in data size be a > factor? though disk is only about 18% full). > Originally it hanged and console had complains about increasing > PMAP_SHPGPERPROC and maxproc. > After some talk in freebsd-fs, I adjusted these parameters and now it > just > hangs without complaining =(( > > Any suggestions? In addition to this PR, I found a couple of similar threads in different lists but they all just have some initial talk and preliminary analysis, and then it just stops. Was that snapshot problem fixed or is it the same as we are talking now? I can't believe I am the only one in almost 2 years who is (trying to be) doing automated backups... So, if it was fixed, when (which version)? If not, then when it might be and -- in the meantime -- is there any workaround for backups? (The system is the production server on the colocation so doing backups in single-user mode is not practical). Thank you in advance Eugene From owner-freebsd-fs@FreeBSD.ORG Thu Mar 23 21:04:29 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C95C816A420 for ; Thu, 23 Mar 2006 21:04:29 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 521AB43D46 for ; Thu, 23 Mar 2006 21:04:29 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 3A9301A4E8F; Thu, 23 Mar 2006 13:04:29 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9EBC2515BE; Thu, 23 Mar 2006 16:04:27 -0500 (EST) Date: Thu, 23 Mar 2006 16:04:27 -0500 From: Kris Kennaway To: Eugene Message-ID: <20060323210426.GA87297@xor.obsecurity.org> References: <20060322120033.E5B8916A44B@hub.freebsd.org> <007801c64eb9$3db4c050$1b12c055@genie> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5mCyUwZo2JvN/JJP" Content-Disposition: inline In-Reply-To: <007801c64eb9$3db4c050$1b12c055@genie> User-Agent: Mutt/1.4.2.1i Cc: freebsd-fs@freebsd.org, Kris Kennaway Subject: Re: UFS2 Snapshots in 6.1-Beta4 - Confirmed Problems 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, 23 Mar 2006 21:04:29 -0000 --5mCyUwZo2JvN/JJP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 23, 2006 at 11:34:40PM +0300, Eugene wrote: > Hi all! >=20 > While we're on the topic of snapshots, I recently posted this follow-up t= o=20 > the PR kern/66270 "[hang] dump causes machine freeze" >=20 > >I wonder what is the status of this PR? > > I seem to have the same problem with 5.3-RELEASE. > > > > Before this started, system worked nicely for more than a year and then= =20 > >it > > started to hang during dump (seemingly just after mksnap_ffs) first > > intermittently and now reproducibly (might increase in data size be a > > factor? though disk is only about 18% full). > > Originally it hanged and console had complains about increasing > > PMAP_SHPGPERPROC and maxproc. > > After some talk in freebsd-fs, I adjusted these parameters and now it= =20 > >just > > hangs without complaining =3D(( > > > > Any suggestions? >=20 > In addition to this PR, I found a couple of similar threads in different= =20 > lists but they all just have some initial talk and preliminary analysis,= =20 > and then it just stops. Was that snapshot problem fixed or is it the same= =20 > as we are talking now? I can't believe I am the only one in almost 2 year= s=20 > who is (trying to be) doing automated backups... > So, if it was fixed, when (which version)? If not, then when it might be= =20 > and -- in the meantime -- is there any workaround for backups? (The syste= m=20 > is the production server on the colocation so doing backups in single-use= r=20 > mode is not practical). 6.1. Kris --5mCyUwZo2JvN/JJP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEIw1ZWry0BWjoQKURAn+NAJ9trkPCeLdkNqTKc+C1lksGyf3WSgCeOrC5 r/Gzo0qio59eRQdUrvp/3Yc= =pBL/ -----END PGP SIGNATURE----- --5mCyUwZo2JvN/JJP-- From owner-freebsd-fs@FreeBSD.ORG Thu Mar 23 21:16:51 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1248A16A423 for ; Thu, 23 Mar 2006 21:16:51 +0000 (UTC) (envelope-from julien.gabel@thilelli.net) Received: from smtp.thilelli.net (smtp.thilelli.net [62.212.120.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 05E5743D4C for ; Thu, 23 Mar 2006 21:16:49 +0000 (GMT) (envelope-from julien.gabel@thilelli.net) Received: from localhost (localhost [127.0.0.1]) by bento.thilelli.net (Postfix) with ESMTP id 842A02E061; Thu, 23 Mar 2006 22:16:48 +0100 (CET) Received: from bento.thilelli.net ([127.0.0.1]) by localhost (bento.thilelli.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 50613-05; Thu, 23 Mar 2006 22:16:47 +0100 (CET) Received: from webmail.thilelli.net (localhost [127.0.0.1]) by bento.thilelli.net (Postfix) with ESMTP id 680122E00D; Thu, 23 Mar 2006 22:16:47 +0100 (CET) Received: from 192.168.1.101 (SquirrelMail authenticated user jgabel) by webmail.thilelli.net with HTTP; Thu, 23 Mar 2006 22:16:47 +0100 (CET) Message-ID: <50319.192.168.1.101.1143148607.squirrel@webmail.thilelli.net> In-Reply-To: <007801c64eb9$3db4c050$1b12c055@genie> References: <20060322120033.E5B8916A44B@hub.freebsd.org> <007801c64eb9$3db4c050$1b12c055@genie> Date: Thu, 23 Mar 2006 22:16:47 +0100 (CET) From: "Julien Gabel" To: "Eugene" User-Agent: SquirrelMail/1.4.6 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: amavisd-new at thilelli.net Cc: freebsd-fs@freebsd.org, Kris Kennaway Subject: Re: UFS2 Snapshots in 6.1-Beta4 - Confirmed Problems. 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, 23 Mar 2006 21:16:51 -0000 > While we're on the topic of snapshots, I recently posted this follow-up to > the PR kern/66270 "[hang] dump causes machine freeze" >> I wonder what is the status of this PR? >> I seem to have the same problem with 5.3-RELEASE. >> >> Before this started, system worked nicely for more than a year and then >> it >> started to hang during dump (seemingly just after mksnap_ffs) first >> intermittently and now reproducibly (might increase in data size be a >> factor? though disk is only about 18% full). >> Originally it hanged and console had complains about increasing >> PMAP_SHPGPERPROC and maxproc. >> After some talk in freebsd-fs, I adjusted these parameters and now it >> just hangs without complaining =(( >> >> Any suggestions? > In addition to this PR, I found a couple of similar threads in different > lists but they all just have some initial talk and preliminary analysis, > and then it just stops. Was that snapshot problem fixed or is it the same > as we are talking now? I can't believe I am the only one in almost 2 > years who is (trying to be) doing automated backups... > So, if it was fixed, when (which version)? If not, then when it might be > and -- in the meantime -- is there any workaround for backups? (The system > is the production server on the colocation so doing backups in single-user > mode is not practical). Interesting. I used dump/restore without problem on i386 using a file system of 120Go. I swiched two weeks ago on amd64 using a file system of 260Go and encountered the very same behaviour (hang, freeze). Don't know if it is related to the new processor architecture or the bigger fs size, but i didn't observe this hang on smallest file system before. Because i am a big fan of dump, i currently choose to use it without the '-L' switch, back to the old (classical?) behaviour, i.e. not doing a snapshot before doing the dump. It is always better than not having complete system backup at all (YMMV, though). I am currently running 6.1-PRERELEASE build Wed Mar 22 03:55:42 CET 2006. -- -jpeg. From owner-freebsd-fs@FreeBSD.ORG Thu Mar 23 21:39:44 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1BA0B16A428 for ; Thu, 23 Mar 2006 21:39:44 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38B7843D64 for ; Thu, 23 Mar 2006 21:39:42 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 211591A4E8F; Thu, 23 Mar 2006 13:39:42 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 88F0151965; Thu, 23 Mar 2006 16:39:41 -0500 (EST) Date: Thu, 23 Mar 2006 16:39:41 -0500 From: Kris Kennaway To: Julien Gabel Message-ID: <20060323213941.GA88109@xor.obsecurity.org> References: <20060322120033.E5B8916A44B@hub.freebsd.org> <007801c64eb9$3db4c050$1b12c055@genie> <50319.192.168.1.101.1143148607.squirrel@webmail.thilelli.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50319.192.168.1.101.1143148607.squirrel@webmail.thilelli.net> User-Agent: Mutt/1.4.2.1i Cc: Eugene , freebsd-fs@freebsd.org, Kris Kennaway Subject: Re: UFS2 Snapshots in 6.1-Beta4 - Confirmed Problems. 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, 23 Mar 2006 21:39:44 -0000 On Thu, Mar 23, 2006 at 10:16:47PM +0100, Julien Gabel wrote: > > While we're on the topic of snapshots, I recently posted this follow-up to > > the PR kern/66270 "[hang] dump causes machine freeze" > > >> I wonder what is the status of this PR? > >> I seem to have the same problem with 5.3-RELEASE. > >> > >> Before this started, system worked nicely for more than a year and then > >> it > >> started to hang during dump (seemingly just after mksnap_ffs) first > >> intermittently and now reproducibly (might increase in data size be a > >> factor? though disk is only about 18% full). > >> Originally it hanged and console had complains about increasing > >> PMAP_SHPGPERPROC and maxproc. > >> After some talk in freebsd-fs, I adjusted these parameters and now it > >> just hangs without complaining =(( > >> > >> Any suggestions? > > > In addition to this PR, I found a couple of similar threads in different > > lists but they all just have some initial talk and preliminary analysis, > > and then it just stops. Was that snapshot problem fixed or is it the same > > as we are talking now? I can't believe I am the only one in almost 2 > > years who is (trying to be) doing automated backups... > > So, if it was fixed, when (which version)? If not, then when it might be > > and -- in the meantime -- is there any workaround for backups? (The system > > is the production server on the colocation so doing backups in single-user > > mode is not practical). > > Interesting. I used dump/restore without problem on i386 using a file > system of 120Go. I swiched two weeks ago on amd64 using a file system of > 260Go and encountered the very same behaviour (hang, freeze). Don't know > if it is related to the new processor architecture or the bigger fs size, > but i didn't observe this hang on smallest file system before. > > Because i am a big fan of dump, i currently choose to use it without the > '-L' switch, back to the old (classical?) behaviour, i.e. not doing a > snapshot before doing the dump. It is always better than not having > complete system backup at all (YMMV, though). > > I am currently running 6.1-PRERELEASE build Wed Mar 22 03:55:42 CET 2006. Let us know if it recurs with your updated kernel. Kris From owner-freebsd-fs@FreeBSD.ORG Fri Mar 24 09:32:59 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF81A16A401 for ; Fri, 24 Mar 2006 09:32:59 +0000 (UTC) (envelope-from bde@zeta.org.au) Received: from mailout2.pacific.net.au (mailout2.pacific.net.au [61.8.0.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20C9743D4C for ; Fri, 24 Mar 2006 09:32:59 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.0.87]) by mailout2.pacific.net.au (Postfix) with ESMTP id C459D16DE03; Fri, 24 Mar 2006 20:32:57 +1100 (EST) Received: from epsplex.bde.org (katana.zip.com.au [61.8.7.246]) by mailproxy2.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id k2O9WtEu022061; Fri, 24 Mar 2006 20:32:56 +1100 Date: Fri, 24 Mar 2006 20:32:55 +1100 (EST) From: Bruce Evans X-X-Sender: bde@epsplex.bde.org To: Nicolas KOWALSKI In-Reply-To: Message-ID: <20060324194552.J6509@epsplex.bde.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@freebsd.org Subject: Re: quotas problem on 4.11/UFS 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, 24 Mar 2006 09:32:59 -0000 On Thu, 23 Mar 2006, Nicolas KOWALSKI wrote: > Our FreeBSD 4.11 fileserver (NFS, Samba) seems to have some problems > with quotas, apparently just after a lot of files are deleted. The > clients are mostly Linux 2.6 workstations (75), and some Windows XP > (10). > > For example, yesterday the quota files of one disk were these: > > -rw-r----- 1 root tty 2097120 Mar 21 23:14 quota.group > -rw-r----- 1 root tty 2097120 Mar 21 23:14 quota.user > > > But today, after a user deleted a lot of his files, the quotas files > are: > > -rw-r----- 1 root tty 2097120 Mar 22 23:10 quota.group > -rw-r----- 1 root tty 4294967264 Mar 22 23:10 quota.user IIRC, quota maps are sparse, with uid N mapped to offset N*sizeof(somestruct). With 32-bit uids, N can be as large as 4294967295, so the file size wants to be (this+1)*sizeof(somestruct) = some not very large multiple of 4GB. The large file sizes for this might even work, without wasting much disk space, since files can be sparse too, but there may be overflow problems at 4G. Your magic size of 4294967264 is 4G-32. 4G-2 is a common large uid; it is produced by nfs's default mapping of the root uid (nfs spells this id bogusly as -2, but uids are unsigned so it becomes a very large unsigned value (but "very large" is only 65334 with 16-bit uids)). Your magic file size would be explained by sizeof(somestruct) being 32 and the magic uid N = (uint32_t)-2 being used. Then (N+1)*sizeof(somestruct) gives 4G-32 after overflow in the multiplication. > The repquota command still works, but takes more time (30 secs instead > of immediate). The slowness is because even sparse files take a long time to process if they are large. repquota apparently has to search through almost 4GB of zeros before it gets to data for the big uid at the end. Then after wasting a lot of time to the nonzero data at the end, this data will probably be misprocessed due to the multiplication overflow. > We will reboot the server today to rebuild the quota files. > > Does anyone know what is happenning here, and if possible how to > prevent it ? Thanks. It seems to be necessary to limit uids to a fairly small value to work around the quota bugs. Limiting them to something like 4G/32 would avoid the overflow bugs (if any) or prevent file sizes of something like 4G*32 if there are no overflow bugs. But limiting them is not so easy for remote access. A remote system may have too many large uids for remapping them all to be practical. nfs has the maproot directive in /etc/exports to support mapping the root uid to anything (default -2) but it doesn't seem to support mapping other uids individually (it has mapall to map them all to the same (?) uid). There might be PRs with more details about this. PR38156 just reports that quota -2 doesn't work. It gives the same magic number 4G-32 for the size of quota.user and the magic number 4G-2 in error output from quotcheck, but other details are different: quota.user was copied from a Sun system, and quotacheck is apparently failing by trying to seek to offset (4G-2)*sizeof(somestruct) where data for this uid should be found, so it seems that the Sun system had multiplication overflow bugs but quotacheck doesn't. Bruce From owner-freebsd-fs@FreeBSD.ORG Fri Mar 24 11:58:13 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7138D16A400 for ; Fri, 24 Mar 2006 11:58:13 +0000 (UTC) (envelope-from jpeg@thilelli.net) Received: from smtp.thilelli.net (smtp.thilelli.net [62.212.120.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81E8F43D49 for ; Fri, 24 Mar 2006 11:58:12 +0000 (GMT) (envelope-from jpeg@thilelli.net) Received: from localhost (localhost [127.0.0.1]) by bento.thilelli.net (Postfix) with ESMTP id 244982E073; Fri, 24 Mar 2006 12:58:11 +0100 (CET) Received: from bento.thilelli.net ([127.0.0.1]) by localhost (bento.thilelli.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 08161-05; Fri, 24 Mar 2006 12:58:10 +0100 (CET) Received: from webmail.thilelli.net (localhost [127.0.0.1]) by bento.thilelli.net (Postfix) with ESMTP id E3C5D2E06A; Fri, 24 Mar 2006 12:58:09 +0100 (CET) Received: from 145.248.192.4 (SquirrelMail authenticated user jgabel) by webmail.thilelli.net with HTTP; Fri, 24 Mar 2006 12:58:09 +0100 (CET) Message-ID: <59591.145.248.192.4.1143201489.squirrel@webmail.thilelli.net> In-Reply-To: <20060323213941.GA88109@xor.obsecurity.org> References: <20060322120033.E5B8916A44B@hub.freebsd.org> <007801c64eb9$3db4c050$1b12c055@genie> <50319.192.168.1.101.1143148607.squirrel@webmail.thilelli.net> <20060323213941.GA88109@xor.obsecurity.org> Date: Fri, 24 Mar 2006 12:58:09 +0100 (CET) From: "Julien Gabel" To: "Kris Kennaway" User-Agent: SquirrelMail/1.4.6 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: amavisd-new at thilelli.net Cc: Eugene , freebsd-fs@freebsd.org Subject: Re: UFS2 Snapshots in 6.1-Beta4 - Confirmed Problems. 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, 24 Mar 2006 11:58:13 -0000 >>> While we're on the topic of snapshots, I recently posted this >>> follow-up to the PR kern/66270 "[hang] dump causes machine freeze" >>>> I wonder what is the status of this PR? >>>> I seem to have the same problem with 5.3-RELEASE. >>>> >>>> Before this started, system worked nicely for more than a year and >>>> then it started to hang during dump (seemingly just after mksnap_ffs) >>>> first intermittently and now reproducibly (might increase in data >>>> size be a factor? though disk is only about 18% full). >>>> Originally it hanged and console had complains about increasing >>>> PMAP_SHPGPERPROC and maxproc. >>>> After some talk in freebsd-fs, I adjusted these parameters and now >>>> it just hangs without complaining =(( >>>> >>>> Any suggestions? >>> In addition to this PR, I found a couple of similar threads in >>> different lists but they all just have some initial talk and >>> preliminary analysis, and then it just stops. Was that snapshot >>> problem fixed or is it the same as we are talking now? I can't >>> believe I am the only one in almost 2 years who is (trying to be) >>> doing automated backups... >>> So, if it was fixed, when (which version)? If not, then when it might >>> be and -- in the meantime -- is there any workaround for backups? >>> (The system is the production server on the colocation so doing >>> backups in single-user mode is not practical). >> Interesting. I used dump/restore without problem on i386 using a file >> system of 120Go. I swiched two weeks ago on amd64 using a file system >> of 260Go and encountered the very same behavior (hang, freeze). Don't >> know if it is related to the new processor architecture or the bigger >> fs size, but i didn't observe this hang on smallest file system before. >> >> Because i am a big fan of dump, i currently choose to use it without the >> '-L' switch, back to the old (classical?) behavior, i.e. not doing a >> snapshot before doing the dump. It is always better than not having >> complete system backup at all (YMMV, though). >> >> I am currently running 6.1-PRERELEASE build Wed Mar 22 03:55:42 CET >> 2006. > Let us know if it recurs with your updated kernel. Well, it seems ok now with FreeBSD 6.1-PRERELEASE #0 Fri Mar 24 03:58 CET 2006. During the creation of the snapshot (either with mksnap_ffs(8) or with `dump -L'), the system was not particularly "responsiveness", but it seems to be the expected behavior. FYI, for an UFSv2 file system of 260Go with currently ~6.5Go used, it took approximatively ~15mn (on recent hardware). Globally, and minus the ~15mn of not very good serviceability (http requests time-out -- or very, very slow to be served -- and interactive shells not very responsive), all seems ok : the snapshot doesn't hang or freeze the system globally anymore, and the backup are made correctly using `dump -L'). So, good news. -- -jpeg. From owner-freebsd-fs@FreeBSD.ORG Fri Mar 24 13:08:36 2006 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A39816A41F for ; Fri, 24 Mar 2006 13:08:36 +0000 (UTC) (envelope-from Nicolas.Kowalski@imag.fr) Received: from imag.imag.fr (imag.imag.fr [129.88.30.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 574E743D49 for ; Fri, 24 Mar 2006 13:08:35 +0000 (GMT) (envelope-from Nicolas.Kowalski@imag.fr) Received: from mail-veri.imag.fr (mail-veri.imag.fr [129.88.43.52]) by imag.imag.fr (8.13.0/8.13.0) with ESMTP id k2OD8V6n016927 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Fri, 24 Mar 2006 14:08:31 +0100 (CET) Received: from corbeau.imag.fr ([129.88.43.162]) by mail-veri.imag.fr with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1FMm1n-0005KV-OJ for freebsd-fs@FreeBSD.org; Fri, 24 Mar 2006 14:08:31 +0100 Received: from kowalski by corbeau.imag.fr with local (Exim 4.50) id 1FMm1m-0006V9-Om for freebsd-fs@FreeBSD.org; Fri, 24 Mar 2006 14:08:30 +0100 To: freebsd-fs@FreeBSD.org References: <20060324194552.J6509@epsplex.bde.org> From: Nicolas KOWALSKI Date: Fri, 24 Mar 2006 14:08:30 +0100 In-Reply-To: <20060324194552.J6509@epsplex.bde.org> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: Nicolas Kowalski X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.6 (imag.imag.fr [129.88.30.1]); Fri, 24 Mar 2006 14:08:31 +0100 (CET) X-IMAG-MailScanner: Found to be clean X-IMAG-MailScanner-Information: Please contact the ISP for more information Cc: Subject: Re: quotas problem on 4.11/UFS 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, 24 Mar 2006 13:08:36 -0000 Bruce Evans writes: > On Thu, 23 Mar 2006, Nicolas KOWALSKI wrote: > >> Our FreeBSD 4.11 fileserver (NFS, Samba) seems to have some problems >> with quotas, apparently just after a lot of files are deleted. The >> clients are mostly Linux 2.6 workstations (75), and some Windows XP >> (10). >> >> For example, yesterday the quota files of one disk were these: >> >> -rw-r----- 1 root tty 2097120 Mar 21 23:14 quota.group >> -rw-r----- 1 root tty 2097120 Mar 21 23:14 quota.user >> >> >> But today, after a user deleted a lot of his files, the quotas files >> are: >> >> -rw-r----- 1 root tty 2097120 Mar 22 23:10 quota.group >> -rw-r----- 1 root tty 4294967264 Mar 22 23:10 quota.user > > IIRC, quota maps are sparse, with uid N mapped to offset > N*sizeof(somestruct). With 32-bit uids, N can be as large as > 4294967295, so the file size wants to be (this+1)*sizeof(somestruct) = > some not very large multiple of 4GB. The large file sizes for this > might even work, without wasting much disk space, since files can be > sparse too, but there may be overflow problems at 4G. > > Your magic size of 4294967264 is 4G-32. 4G-2 is a common large uid; > it is produced by nfs's default mapping of the root uid (nfs spells > this id bogusly as -2, but uids are unsigned so it becomes a very > large unsigned value (but "very large" is only 65334 with 16-bit > uids)). Your magic file size would be explained by > sizeof(somestruct) being 32 and the magic uid N = (uint32_t)-2 being > used. Then (N+1)*sizeof(somestruct) gives 4G-32 after overflow in > the multiplication. Many thanks for this explanation. However, the filesystem does not have any files belonging to some user with a large or -2 uid. I checked it, and even "quotacheck -v" does not show anything like that; our current uids goes from 0 to 6000 max, and only these appear in the repquota result. -- Nicolas From owner-freebsd-fs@FreeBSD.ORG Fri Mar 24 13:48:11 2006 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3C5716A401 for ; Fri, 24 Mar 2006 13:48:11 +0000 (UTC) (envelope-from bde@zeta.org.au) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3365343D45 for ; Fri, 24 Mar 2006 13:48:11 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.0.87]) by mailout1.pacific.net.au (Postfix) with ESMTP id E0BF7347CB5; Sat, 25 Mar 2006 00:48:09 +1100 (EST) Received: from epsplex.bde.org (katana.zip.com.au [61.8.7.246]) by mailproxy2.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id k2ODm7qI017071; Sat, 25 Mar 2006 00:48:08 +1100 Date: Sat, 25 Mar 2006 00:48:07 +1100 (EST) From: Bruce Evans X-X-Sender: bde@epsplex.bde.org To: Nicolas KOWALSKI In-Reply-To: Message-ID: <20060325004132.P7231@epsplex.bde.org> References: <20060324194552.J6509@epsplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@FreeBSD.org Subject: Re: quotas problem on 4.11/UFS 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, 24 Mar 2006 13:48:11 -0000 On Fri, 24 Mar 2006, Nicolas KOWALSKI wrote: > Bruce Evans writes: >> IIRC, quota maps are sparse, with uid N mapped to offset >> N*sizeof(somestruct). With 32-bit uids, N can be as large as >> 4294967295, so the file size wants to be (this+1)*sizeof(somestruct) = >> some not very large multiple of 4GB. The large file sizes for this >> might even work, without wasting much disk space, since files can be >> sparse too, but there may be overflow problems at 4G. >> ... > > Many thanks for this explanation. > > However, the filesystem does not have any files belonging to some user > with a large or -2 uid. I checked it, and even "quotacheck -v" does > not show anything like that; our current uids goes from 0 to 6000 max, > and only these appear in the repquota result. Perhaps it had them but there were none when you checked. I think the quota file doesn't shrink if slots at the end of int become unused. Files with a uid of -2 are created on nfs clients if root is not mapped and root creates a file. I see quite a lot of them due to having a world-writeable /c/tmp directory and using it as root on the client. Bruce From owner-freebsd-fs@FreeBSD.ORG Fri Mar 24 15:15:29 2006 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2AB4B16A401 for ; Fri, 24 Mar 2006 15:15:29 +0000 (UTC) (envelope-from Nicolas.Kowalski@imag.fr) Received: from imag.imag.fr (imag.imag.fr [129.88.30.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E10143D45 for ; Fri, 24 Mar 2006 15:15:28 +0000 (GMT) (envelope-from Nicolas.Kowalski@imag.fr) Received: from mail-veri.imag.fr (mail-veri.imag.fr [129.88.43.52]) by imag.imag.fr (8.13.0/8.13.0) with ESMTP id k2OFFM30020403 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Fri, 24 Mar 2006 16:15:22 +0100 (CET) Received: from corbeau.imag.fr ([129.88.43.162]) by mail-veri.imag.fr with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1FMo0Y-0008AX-Jz for freebsd-fs@FreeBSD.org; Fri, 24 Mar 2006 16:15:22 +0100 Received: from kowalski by corbeau.imag.fr with local (Exim 4.50) id 1FMo0Y-0006r7-FI for freebsd-fs@FreeBSD.org; Fri, 24 Mar 2006 16:15:22 +0100 To: freebsd-fs@FreeBSD.org References: <20060324194552.J6509@epsplex.bde.org> <20060325004132.P7231@epsplex.bde.org> From: Nicolas KOWALSKI Date: Fri, 24 Mar 2006 16:15:22 +0100 In-Reply-To: <20060325004132.P7231@epsplex.bde.org> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: Nicolas Kowalski X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.6 (imag.imag.fr [129.88.30.1]); Fri, 24 Mar 2006 16:15:22 +0100 (CET) X-IMAG-MailScanner: Found to be clean X-IMAG-MailScanner-Information: Please contact the ISP for more information Cc: Subject: Re: quotas problem on 4.11/UFS 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, 24 Mar 2006 15:15:29 -0000 Bruce Evans writes: > On Fri, 24 Mar 2006, Nicolas KOWALSKI wrote: >> However, the filesystem does not have any files belonging to some >> user with a large or -2 uid. I checked it, and even "quotacheck -v" >> does not show anything like that; our current uids goes from 0 to >> 6000 max, and only these appear in the repquota result. > > Perhaps it had them but there were none when you checked. I think > the quota file doesn't shrink if slots at the end of int become > unused. Hm, that is what probably happenned. > Files with a uid of -2 are created on nfs clients if root is not > mapped and root creates a file. I see quite a lot of them due to > having a world-writeable /c/tmp directory and using it as root on > the client. I just reconfigured /etc/exports to force root mapping to some "cleaner and known" uid/gid. Many Thanks for your tips, ideas and explanations ! Best regards, -- Nicolas From owner-freebsd-fs@FreeBSD.ORG Fri Mar 24 16:58:19 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F26516A439 for ; Fri, 24 Mar 2006 16:58:19 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FBCA43D5C for ; Fri, 24 Mar 2006 16:58:13 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id BB40D1A4EC4; Fri, 24 Mar 2006 08:58:13 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id BE97751443; Fri, 24 Mar 2006 11:58:12 -0500 (EST) Date: Fri, 24 Mar 2006 11:58:12 -0500 From: Kris Kennaway To: Julien Gabel Message-ID: <20060324165812.GA24661@xor.obsecurity.org> References: <20060322120033.E5B8916A44B@hub.freebsd.org> <007801c64eb9$3db4c050$1b12c055@genie> <50319.192.168.1.101.1143148607.squirrel@webmail.thilelli.net> <20060323213941.GA88109@xor.obsecurity.org> <59591.145.248.192.4.1143201489.squirrel@webmail.thilelli.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="r5Pyd7+fXNt84Ff3" Content-Disposition: inline In-Reply-To: <59591.145.248.192.4.1143201489.squirrel@webmail.thilelli.net> User-Agent: Mutt/1.4.2.1i Cc: Eugene , freebsd-fs@freebsd.org, Kris Kennaway Subject: Re: UFS2 Snapshots in 6.1-Beta4 - Confirmed Problems. 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, 24 Mar 2006 16:58:19 -0000 --r5Pyd7+fXNt84Ff3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 24, 2006 at 12:58:09PM +0100, Julien Gabel wrote: > > Let us know if it recurs with your updated kernel. >=20 > Well, it seems ok now with FreeBSD 6.1-PRERELEASE #0 Fri Mar 24 03:58 CET > 2006. During the creation of the snapshot (either with mksnap_ffs(8) or > with `dump -L'), the system was not particularly "responsiveness", but it > seems to be the expected behavior. FYI, for an UFSv2 file system of > 260Go with currently ~6.5Go used, it took approximatively ~15mn (on > recent hardware). >=20 > Globally, and minus the ~15mn of not very good serviceability (http > requests time-out -- or very, very slow to be served -- and interactive > shells not very responsive), all seems ok : the snapshot doesn't hang or > freeze the system globally anymore, and the backup are made correctly > using `dump -L'). So, good news. Great, that fits with expectations. Thanks for testing, Kris --r5Pyd7+fXNt84Ff3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEJCUkWry0BWjoQKURAvKVAKDW/V1EMmqck56MkejIqcsrqVT0vACgpuz9 vEeRMpomCx+NN9bLpaDwiOw= =++uf -----END PGP SIGNATURE----- --r5Pyd7+fXNt84Ff3-- From owner-freebsd-fs@FreeBSD.ORG Fri Mar 24 21:47:17 2006 Return-Path: X-Original-To: fs@freebsd.org Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B46116A427 for ; Fri, 24 Mar 2006 21:47:17 +0000 (UTC) (envelope-from mi+mx@aldan.algebra.com) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCC2143D48 for ; Fri, 24 Mar 2006 21:47:16 +0000 (GMT) (envelope-from mi+mx@aldan.algebra.com) Received: from corbulon.video-collage.com (static-151-204-231-237.bos.east.verizon.net [151.204.231.237]) by aldan.algebra.com (8.13.6/8.13.6) with ESMTP id k2OLlC7D002903 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 24 Mar 2006 16:47:15 -0500 (EST) (envelope-from mi+mx@aldan.algebra.com) Received: from mteterin.us.murex.com (195-11.customer.cloud9.net [168.100.195.11]) by corbulon.video-collage.com (8.13.6/8.13.6) with ESMTP id k2OLl56B053727 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 24 Mar 2006 16:47:06 -0500 (EST) (envelope-from mi+mx@aldan.algebra.com) Received: from mteterin.us.murex.com (mteterin@localhost [127.0.0.1]) by mteterin.us.murex.com (8.13.4/8.13.4) with ESMTP id k2OLl0BO044648 for ; Fri, 24 Mar 2006 16:47:00 -0500 (EST) (envelope-from mi+mx@aldan.algebra.com) Received: from localhost (localhost [[UNIX: localhost]]) by mteterin.us.murex.com (8.13.4/8.13.4/Submit) id k2OLkwJV044647 for fs@freebsd.org; Fri, 24 Mar 2006 16:46:58 -0500 (EST) (envelope-from mi+mx@aldan.algebra.com) X-Authentication-Warning: mteterin.us.murex.com: mteterin set sender to mi+mx@aldan.algebra.com using -f From: Mikhail Teterin Organization: Virtual Estates, Inc. To: fs@freebsd.org Date: Fri, 24 Mar 2006 16:46:58 -0500 User-Agent: KMail/1.8.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603241646.58415.mi+mx@aldan.algebra.com> X-Virus-Scanned: ClamAV devel-20050525/1356/Fri Mar 24 13:41:06 2006 on corbulon.video-collage.com X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.43 Cc: Subject: How 'honest' is fstat(1)? 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, 24 Mar 2006 21:47:17 -0000 Hello! As a policy I try to keep my /, /usr, and other filesystems (except /var and /home) mounted readonly. (Not so much for security as for safety.) When I need to make a modification, I remount them: mount -orw -u / make the change, and remount back: mount -oro -u /usr/local This works for "small" changes, but sometimes, however, after a bigger on (such as rebuilding of some ports), the last step fails with "busy". At this time nothing should have a file open, and nothing does according to fstat. The command: fstat | awk '$5 == "/usr/local" && $NF != "r"' does not list anything. Yet, the fs (in this case -- /usr/local) will not remount readonly. My only guess is, the earlier versions of the just reinstalled executables are still running and that trigger's the rarely noticed bug. Any other guesses? Thanks! -mi