From owner-freebsd-current@FreeBSD.ORG Sat Jun 13 17:04:03 2015 Return-Path: Delivered-To: freebsd-current@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B33C7588 for ; Sat, 13 Jun 2015 17:04:03 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 72514CB4 for ; Sat, 13 Jun 2015 17:04:03 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by oial131 with SMTP id l131so4073910oia.3 for ; Sat, 13 Jun 2015 10:04:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=2Aiiwvh7ryNRK0fOsRPVt1fBeblUSvgPFJSpp//r6jE=; b=yH7lZmje07VsK3yNulpNux45K5lPfX7dTK72l8/FFaXc1Fi+MRcuCAXdbBQPbd/4u6 HR7EePypIxi+68rOP4ZDxK1BXRCCa0hmV/i01o/2TkB2OD3uHStqDQSbWQM2g/bnI0yP K6os/Qh4GhV3kzHY6F98qulPj3+IpcFD5Za7BiiJqb2V2wrGErpPVJJNILP68DQWouOw kD1iTq4/rxCqZ20CngB0wxqLLSZp0NieFIEdDiAnBAaQNCkb6nU96NX9UEB6IzlLK4H5 nr07e0cCrcMr9cQX61sqpexyF1VqK30jlLu0zwfv13rqilFtKcdUWQSvHoFxlQJqIeUJ UFIw== MIME-Version: 1.0 X-Received: by 10.202.188.139 with SMTP id m133mr16137000oif.73.1434215042747; Sat, 13 Jun 2015 10:04:02 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.202.221.69 with HTTP; Sat, 13 Jun 2015 10:04:02 -0700 (PDT) In-Reply-To: References: Date: Sat, 13 Jun 2015 10:04:02 -0700 X-Google-Sender-Auth: 9aBNhDE_3kzoP5aUl4UAAvbqKhU Message-ID: Subject: Re: Slow shutdown From: Kevin Oberman To: "Ranjan1018 ." <214748mv@gmail.com> Cc: Henry Hu , Garrett Cooper , FreeBSD CURRENT Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jun 2015 17:04:03 -0000 On Fri, Jun 12, 2015 at 1:30 AM, Ranjan1018 . <214748mv@gmail.com> wrote: > > > 2015-06-12 1:13 GMT+02:00 Henry Hu : > >> On Thu, Jun 11, 2015 at 1:55 PM Kevin Oberman >> wrote: >> >>> The same issue exists in fusefs, but has an uglier result. The fuse >>> daemon >>> shuts down before any fusefs based file systems are unmounted, but, for >>> several R/W file systems including NTFS and exFAT, the result is a >>> corrupt >>> file system. I did the same thing to work around this problem... an init >>> script, but I wonder if this should not be handled in some cleaner and >>> more >>> global manner. (No, I have no idea right now of how to implement this.) >>> >> >> I think that I've hit this problem several times, because I've lost files >> on my NTFS portable harddisk several times. Now I force an unmount in the >> shutdown script. >> I remember that when fuse module was still in fusefs-kmod, the rc script >> unmounts the file systems, and there's even a _safe flag to ensure safety. >> >> > Hi, > I have the same issue in my laptop a dual boot FreeBSD/Windows 8. In > FreeBSD, the Win8 partition, is mounted via fusefs and is unmounted in a > shutdown script. > But if I do not unmount this partition in a script, it is not unmounted by > the OS or fusefs at shutdown. Probably this is a different or new bug. > > For the original bug I have opened a PR: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200784 > Please comment here if you like. > > Regards, > Maurizio > > I also opened a bug report for the fusefs case. It is https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200513. It includes a shutdown script that will unmount the file systems cleanly, though it will unmount all fusefs file systems, whether they need it or not. Many fusefs file systems are read-only or fully synchronous, so are always "clean". But, as far as I can tell, unmounting does not harm for any fusefs file system. (Yes, "fusefs file system" is probably redundant.) The shutdown script is only for systems running the native fusefs code and not the older fusefs-kmod port. -- Kevin Oberman, Network Engineer, Retired