From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id EE4F913877A for ; Sat, 28 Jun 2014 14:50:31 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E45A2E08E2; Sat, 28 Jun 2014 14:50:25 +0000 (UTC) Received: from smarthost01b.mail.zen.net.uk (smarthost01b.mail.zen.net.uk [212.23.1.3]) by pigeon.gentoo.org (Postfix) with ESMTP id 58D55E088F for ; Sat, 28 Jun 2014 14:50:24 +0000 (UTC) Received: from [82.69.80.10] (helo=wstn.localnet) by smarthost01b.mail.zen.net.uk with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1X0txP-0008FO-JV for gentoo-user@lists.gentoo.org; Sat, 28 Jun 2014 14:50:23 +0000 From: Peter Humphrey To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: smartctrl drive error @60% Date: Sat, 28 Jun 2014 15:50:23 +0100 Message-ID: <5415805.nsLkOMKIlt@wstn> Organization: at home User-Agent: KMail/4.12.5 (Linux/3.12.21-gentoo-r1; KDE/4.12.5; x86_64; ; ) In-Reply-To: <53AECE13.1020006@gmail.com> References: <53AA050F.4070907@gmail.com> <53AEC9FA.7070404@gmail.com> <53AECE13.1020006@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Originating-smarthost01b-IP: [82.69.80.10] X-Archives-Salt: 28b80dbe-87d8-4c55-9d4e-f6b91fecb309 X-Archives-Hash: 0db31970a25f0976adc4ba1905bf95d6 On Saturday 28 June 2014 09:15:47 Dale wrote: > > Alan McKinnon wrote: --->8 > >> But that's not your main problem. You got those filenames because the > >> source disk somehow has a problem and the names couldn't be read > >> properly. So junk was used instead. I thought it was more like: the file lister didn't recognise those bytes as valid characters so it printed a question-mark for each of them. If it is so, it's no use Dale looking for files with question-marks in their names. --->8 > It listed some files with a question mark in it but not the ones I am > looking for. So, is it possible that since it couldn't read the file it > just skipped them? It may not be true that it couldn't read the files; it just couldn't translate their names into text characters. The names are not held in the files whose names they are but somewhere in the inode structure. Someone with better knowledge of this (i.e.any at all) will have to explain what goes wrong if bytes on the disk adjacent to the file names get damaged along with the names. > I used rsync to do the copy instead of cp. Maybe that is it or otherwise, I > have a ton of directories to go diggin in to find them since it isn't the > one I thought it was. Do you know any characters in those dodgy names, Dale? If so, you may be able to use /usr/bin/find like so (hoping this isn't a grandma's egg - apologies if it is): find /path-to-files -iname \*known-part-of-name\* {} + -- Regards Peter