From owner-freebsd-questions@freebsd.org Fri Jun 9 07:40:19 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3CD12BD3AA9 for ; Fri, 9 Jun 2017 07:40:19 +0000 (UTC) (envelope-from ml@netfence.it) Received: from smtp205.alice.it (smtp205.alice.it [82.57.200.101]) by mx1.freebsd.org (Postfix) with ESMTP id C9DF781FCB for ; Fri, 9 Jun 2017 07:40:18 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.ventu (87.19.230.171) by smtp205.alice.it (8.6.060.28) (authenticated as acanedi@alice.it) id 5937FCBE05ADA65F; Fri, 9 Jun 2017 09:35:06 +0200 Received: from alamar.ventu (alamar.local.netfence.it [10.1.2.18]) by soth.ventu (8.15.2/8.15.2) with ESMTP id v597Z2Zm090411; Fri, 9 Jun 2017 09:35:02 +0200 (CEST) (envelope-from ml@netfence.it) X-Authentication-Warning: soth.ventu: Host alamar.local.netfence.it [10.1.2.18] claimed to be alamar.ventu Subject: Re: Panic on external HD disconnection To: Polytropon Cc: freebsd-questions@freebsd.org References: <929de353-94c4-cbf2-9b33-67f60b007a71@netfence.it> <20170608204740.9ad9b1c3.freebsd@edvax.de> From: Andrea Venturoli Message-ID: Date: Fri, 9 Jun 2017 09:35:02 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <20170608204740.9ad9b1c3.freebsd@edvax.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jun 2017 07:40:19 -0000 On 06/08/17 20:47, Polytropon wrote: > So the disk was mounted at that specific point in time? Yes, as I said I was taking a backup, so that disk was mounted and was being written to. > Partially understandable. The system will somehow react > to a mass media device surprisingly removed when it is > writing to it... Yes, *partially* understandable. I just like to know to what extent that "partially" goes. If I am to expect a full panic, it's ok. If, somehow, I could get a partial failure, then something is wrong in my setup and I'll have to investigate. > In case of accidental UFS disconnect, reconnect the drive, > do _not_ attempt to mount it right away, but instead perform > a full fsck ("fsck -yf /dev/da0", for example) of the file > system on that disk. In best case, fsck will repair any > damages that did appear, and then return the file system into > a consistent state, ready for mounting. That's what I did after the system came up again. bye & Thanks av.