Date: Wed, 19 Oct 2016 07:22:18 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Arrigo Marchiori <ardovm@yahoo.it> Cc: Arrigo Marchiori via freebsd-fs <freebsd-fs@freebsd.org> Subject: Re: Random truncated files on USB hard disk with timeouts; how to debug? Message-ID: <7924.1476861738@critter.freebsd.dk> In-Reply-To: <20161019064315.GB93031@nuvolo> References: <20161018152715.GC89691@nuvolo> <51997.1476812624@critter.freebsd.dk> <20161019062812.GA93031@nuvolo> <7759.1476858801@critter.freebsd.dk> <20161019064315.GB93031@nuvolo>
next in thread | previous in thread | raw e-mail | index | archive | help
-------- In message <20161019064315.GB93031@nuvolo>, Arrigo Marchiori writes: >> Y-cables are a big warning sign. >> >> You can try plugging the "power-only" plug into a high quality 1 >> ampere USB charger, but that is no guarantee for success. > >Yes, I also thought so at first. > >But I also believe that if anything goes wrong at the hardware level, >I should get a big warning from the kernel, instead of a funny >apparently-truncated file, that returns to be readable at next >reboot...? Only if the drive finds out something is wrong and tells the kernel. If the drive has bad power supply, that may not happen. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7924.1476861738>