Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S269260AbUIBXL6 (ORCPT ); Thu, 2 Sep 2004 19:11:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S269263AbUIBXI5 (ORCPT ); Thu, 2 Sep 2004 19:08:57 -0400 Received: from c002781a.fit.bostream.se ([217.215.235.8]:40336 "EHLO mail.tnonline.net") by vger.kernel.org with ESMTP id S269281AbUIBXHO (ORCPT ); Thu, 2 Sep 2004 19:07:14 -0400 Date: Fri, 3 Sep 2004 01:06:59 +0200 From: Spam Reply-To: Spam X-Priority: 3 (Normal) Message-ID: <1551538871.20040903010659@tnonline.net> To: Valdis.Kletnieks@vt.edu CC: Oliver Hunt , Helge Hafting , Hans Reiser , Linus Torvalds , David Masover , Jamie Lokier , Horst von Brand , Adrian Bunk , , Christoph Hellwig , , , Alexander Lyamin aka FLX , ReiserFS List Subject: Re: The argument for fs assistance in handling archives In-Reply-To: <200409022239.i82MdmnO015327@turing-police.cc.vt.edu> References: <20040826150202.GE5733@mail.shareable.org> <200408282314.i7SNErYv003270@localhost.localdomain> <20040901200806.GC31934@mail.shareable.org> <20040902002431.GN31934@mail.shareable.org> <413694E6.7010606@slaphack.com> <4136A14E.9010303@slaphack.com> <4136C876.5010806@namesys.com> <4136E0B6.4000705@namesys.com> <4699bb7b04090202121119a57b@mail.gmail.com> <4136E756.8020105@hist.no> <4699bb7b0409020245250922f9@mail.gmail.com> <812032218.20040902120259@tnonline.net> <200409022239.i82MdmnO015327@turing-police.cc.vt.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1384 Lines: 38 > On Thu, 02 Sep 2004 12:02:59 +0200, Spam said: >> The meta-data should be deleted if it the file is copied or moved to >> a medium that doesn't support it. However a _warning_ may be shown >> to the user if there is risk to loose data. > OK... I'll bite. How do you report the warning to the user if you're using > an unenhanced utility to copy a file to a file system that may be lossy? That I do not really know. But I think this is somewhat the discussion here - how to make the support for metas and streams as good as possible. I suppose it would be difficult to actually query the user about something like this unless the applications themselves do. Perhaps warnings in the syslog is good for now? Already now things like advanced attributes get lost when copying data from a supported fs to a non-supported one. Perhaps documentation around the ways to use streams and meta data should mention that only the supported fs will keep the extra info. As long as the user is aware that whatever information he puts in the meta or streams will be lost then it is ok, isn't it? ~S - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/