From owner-freebsd-fs@FreeBSD.ORG Sat Oct 6 06:09:48 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 491B6106564A for ; Sat, 6 Oct 2012 06:09:48 +0000 (UTC) (envelope-from peter.maloney@brockmann-consult.de) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.9]) by mx1.freebsd.org (Postfix) with ESMTP id E32AC8FC08 for ; Sat, 6 Oct 2012 06:09:47 +0000 (UTC) Received: from [192.168.179.201] (hmbg-5f77232a.pool.mediaWays.net [95.119.35.42]) by mrelayeu.kundenserver.de (node=mrbap3) with ESMTP (Nemesis) id 0LsywU-1TQFO91EqY-012UU4; Sat, 06 Oct 2012 08:09:37 +0200 Message-ID: <506FCB19.8010703@brockmann-consult.de> Date: Sat, 06 Oct 2012 08:09:29 +0200 From: Peter Maloney User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120825 Thunderbird/15.0 MIME-Version: 1.0 To: ram_chander250@yahoo.com References: <506C3EFC.2060602@FreeBSD.org> <506D55B5.70403@brockmann-consult.de> In-Reply-To: X-Provags-ID: V02:K0:TTQGlbDrIIK+hH7AkXj2Qu/N3KKiHZaWTDQcnefOvCo EnhUcx0HvHLfgayjOP9ScfkQ6g5TcR1P86I+xrHJpdN1JVa+d+ ujdXXaM4/Ljz6Ig19ljz/SmnajUMQ+5yTEUM3qNdt7aoj4asoN MfNnW8Cd2EcVN/KFwKZ3NaX1Y8ZdNm0AoPhUOj6fMpVFUrG5QW +5UQplxMm4fZYE3FHw/89mC0A1LcQ7NWGzpWXzQSun5/BuY2pL xVAN48Xe19oQBKkjSD/3GCUnbvHKvOFffyRwxy2L2cmWGBDsYZ bVnXC41ydionOknzu6H8AAQALYvSruFWGWz27E/HAfqHc6ai8i Ao2FyexVBYat3vj5G4AQCQ/re4G//53J3vqm7zZ9SmCXGtcrfM OSj/QX62UX17Q== Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: Zfs import issue X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Oct 2012 06:09:48 -0000 Okay, then we have the same problem except I need one more zfs command after the send to hang the filesystem. In my case, this means I can simply never call zfs twice before the first is done. eg. a file based lock in my scripts; or wrap the zfs command with something that locks. Does this solve (workaround) your problem? I find (in 8.2-STABLE, 8.3-STABLE) the file system works 100% during a send unless there is something else with a "zfs" command that happens; only zfs commands will hang/block , not ls, df, etc.; in my example below, I destroyed a snapshot, and that command hung/blocked. And when the hung/blocked zfs command is a write command, such as destroy, then the filesystem is hung/blocked too, including ls, df, etc.. And when a hung/blocked command is killed, it seems to be permanently hung (but could just be enormously slow). On 10/06/2012 05:04 AM, Ram Chander wrote: > Yes importing means "zfs recv" , "df" hangs, "cd " to the filesystem > hangs. Basically entire filesystem is inaccessbile. Once "zfs recv" > completes, all is normal. > > On Thu, Oct 4, 2012 at 2:54 PM, Peter Maloney > > wrote: > > I find this sort of thing to be common, but not exactly as you > describe. > I don't know if I tried df, but "zfs list" hangs (as well as any other > zfs related command, maybe even zdb). And I don't know what you mean > "importing zfs snapshot", so I'm guessing you mean zfs recv. > > eg. > > zfs send somedataset@somesnapshot | ....... > (leave it running in background) > > zfs list > (works fine; I guess it works because send is read-only) > > zfs destroy somedataset@someothersnapshot > (hang; I guess because this is a write operation, so it needs to wait > for the read lock on zfs send to finish the transaction) > > zfs list > (hang) > > I'm not sure if df hangs too. > > At this point, using kill -9 doesn't solve anything, and if you > kill the > zfs send, it's possible that every zfs command and df will hang. > > And I don't know what, but I'm mostly sure there is something I > can run > that will make even "ls" hang after this point. > > > On 10/03/2012 03:34 PM, Andriy Gapon wrote: > > on 03/10/2012 14:43 Ram Chander said the following: > >> Hi, > >> > >> I am importing zfs snapshot to freebsd-9 from anther host running > >> freebsd-9. When the import happens, it locks the filesystem, > "df" hangs > >> and unable to use the filesystem. Once the import completes, > the filesystem > >> is back to normal and read/write works fine. The same doesnt > happen in > >> Solaris/OpenIndiana. > >> > >> # uname -an > >> FreeBSD hostname 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 > 07:46:30 > >> UTC 2012 root@farrell.cse.buffalo.edu:/ > >> usr/obj/usr/src/sys/GENERIC amd64 > >> > >> Zfs ver: 28 > >> > >> > >> Any inputs would be helpful. Is there any way to overcome this > freeze ? > > What if you add -n option to df? > > > > > -- > > -------------------------------------------- > Peter Maloney > Brockmann Consult > Max-Planck-Str. 2 > 21502 Geesthacht > Germany > Tel: +49 4152 889 300 > Fax: +49 4152 889 333 > E-mail: peter.maloney@brockmann-consult.de > > Internet: http://www.brockmann-consult.de > -------------------------------------------- > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to > "freebsd-fs-unsubscribe@freebsd.org > " > >