From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 9 15:53:21 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 02F7E30E for ; Tue, 9 Sep 2014 15:53:21 +0000 (UTC) Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CC686E87 for ; Tue, 9 Sep 2014 15:53:20 +0000 (UTC) Received: by mail-pa0-f46.google.com with SMTP id kq14so2665516pab.33 for ; Tue, 09 Sep 2014 08:53:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=aW/g4nQIRSFZIEU3ejNAdbgou8t7KMU77X5dHBcrb54=; b=gJNeY4KoP00DLXc4L3yuh6SnLPM1U6momM+F23bDwWXuaE9+HjzXOmQlHhsQHjVZV7 EH8+xHAH+HIWi1V9WahzF88rDr/vENtjmMi7y7A9ZVXkddDt+Ilw0Ax8BZEkmLSa+njb wDBLdPFq9HfFqE0a0pZn4EObfpGBVIsALziH1Qvnzy6opUUkMMCUcwywiRxyjGVHLxrM z3m9kOLMwFoEHpWP4uFxQPgygrF3d80TNj9nQqNl4MUXHteI7nTX3ozUMU9UyGq3B7AR wRm2RbSwmAbpObLx4Z9tCy9AVXfyLQujMkFQooKNKPY+MaJRUeGlb68SuE0kW2L9G9wN PsXw== MIME-Version: 1.0 X-Received: by 10.70.133.200 with SMTP id pe8mr13314465pdb.40.1410278000247; Tue, 09 Sep 2014 08:53:20 -0700 (PDT) Received: by 10.66.82.37 with HTTP; Tue, 9 Sep 2014 08:53:20 -0700 (PDT) In-Reply-To: <9F4D2C26-F077-4CA7-A532-BA4CE562C50D@ixsystems.com> References: <755175739.33844219.1410217844431.JavaMail.root@uoguelph.ca> <9F4D2C26-F077-4CA7-A532-BA4CE562C50D@ixsystems.com> Date: Tue, 9 Sep 2014 17:53:20 +0200 Message-ID: Subject: Re: Tool to access ZFS/NFSv4 alternate data streams on FreeBSD? From: Simon Toedt To: Jordan Hubbard Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org, Richard Yao , Rick Macklem , Lionel Cons , Jan Bramkamp X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Sep 2014 15:53:21 -0000 On Tue, Sep 9, 2014 at 6:47 AM, Jordan Hubbard wrote: > Yep. I was just describing the experience that OS X went through in impl= ementing extattrs / legacy resource fork support. To recap it very briefly= : Having NFSv4 support extattrs (or even named streams, if you want to go = that far) is the comparatively easy part. It=E2=80=99s backing them up / c= opying them around that gets more involved, and if you can=E2=80=99t back u= p certain attributes then you=E2=80=99re not likely to get anyone to want t= o use them, at which point the whole =E2=80=9Csharing=E2=80=9D aspect kind = of takes a back seat. The native Solaris tools (tar/pax) and the AT&T AST - written by David Korn himself and used widely within AT&T and customers (i.e. cloud) support resource forks via O_XATTR. CERN also has a large set of applications which rely on O_XATTR, so it seems this is not so uncommon. Simon P.S: Solaris UFS and tmpfs support resource forks via O_XATTR and cd -@ in bash4.3