From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anton Altaparmakov Subject: Re: Print inode number if name can not be represented in the local charset Date: Thu, 21 Jul 2005 14:21:47 +0100 Message-ID: <1121952107.17221.84.camel@imp.csi.cam.ac.uk> References: <1120183436.2758.2.camel@chaos.void> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org Return-path: Received: from ppsw-0.csi.cam.ac.uk ([131.111.8.130]:58573 "EHLO ppsw-0.csi.cam.ac.uk") by vger.kernel.org with ESMTP id S261731AbVGUNVy (ORCPT ); Thu, 21 Jul 2005 09:21:54 -0400 To: Yura Pakhuchiy In-Reply-To: <1120183436.2758.2.camel@chaos.void> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hi Yura, On Fri, 2005-07-01 at 05:03 +0300, Yura Pakhuchiy wrote: > This patch changes message type from ntfs_error to ntfs_debug in the > unistr.c when unicode filename contains characters that can not be > converted into the local charset, because it's not useful for user and > actually it's not a error. Instead of this print warning in dir.c, this > warning includes inode number for further investigation (e.g. with > ntfsinfo). I applied something simillar to your patch to my private tree so it will be in the next ntfs release. Thanks for the patch. Best regards, Anton -- Anton Altaparmakov (replace at with @) Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/