From owner-freebsd-hackers@freebsd.org Mon Feb 19 20:33:54 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 92B50F2238E for ; Mon, 19 Feb 2018 20:33:54 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [IPv6:2001:4cb8:90:ffff::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 280A56A3B2 for ; Mon, 19 Feb 2018 20:33:54 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from router.digiware.nl (localhost.digiware.nl [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 195C42EB0D; Mon, 19 Feb 2018 21:33:52 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.com Received: from smtp.digiware.nl ([127.0.0.1]) by router.digiware.nl (router.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DjyaurV31OhN; Mon, 19 Feb 2018 21:33:51 +0100 (CET) Received: from [192.168.11.152] (unknown [192.168.11.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 2DEF32EB0C; Mon, 19 Feb 2018 21:33:51 +0100 (CET) Subject: Re: Using fstatfs on a ZFS disk To: "Rodney W. Grimes" , rb@gid.co.uk Cc: FreeBSD Hackers References: <201802191833.w1JIXhVL078022@pdx.rh.CN85.dnsmgr.net> From: Willem Jan Withagen Message-ID: <1dfe0d2b-48dd-3f99-8332-b3979faad45d@digiware.nl> Date: Mon, 19 Feb 2018 21:33:53 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <201802191833.w1JIXhVL078022@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: nl Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Feb 2018 20:33:54 -0000 On 19/02/2018 19:33, Rodney W. Grimes wrote: >> Hi, >> >>> On 19 Feb 2018, at 15:50, Willem Jan Withagen wrote: >>> >>> On 19-2-2018 16:00, Bob Bishop wrote: >>>> Hi, >>>>> On 19 Feb 2018, at 14:48, Willem Jan Withagen wrote: >>>>> >>>>> Hi, >>>>> >>>>> I'm trying to find the values of the returned f_type for ZFS >>>>> in the fstatfs call when a file is on ZFS.... >>>>> >>>>> But I have not yet found the definitions of the ENUMS that >>>>> would fill that value... Let alone the value for ZFS. >>>> I chased this particular wild goose myself recently. It?s FS_... in /usr/include/sys/disklabel,h that you want. >>> >>> Hi Bob, >>> >>> I grepped on MAGIC and FS, but the combo did not deliver anything useful. So this is already more that I found. >>> I did get: >>> /usr/include/ufs/ffs/fs.h:#define FS_UFS1_MAGIC 0x011954 /* UFS1 fast filesystem magic number */ >>> /usr/include/ufs/ffs/fs.h:#define FS_UFS2_MAGIC 0x19540119 /* UFS2 fast filesystem magic number */ >>> /usr/include/ufs/ffs/fs.h:#define FS_BAD_MAGIC 0x19960408 /* UFS incomplete newfs magic number */ >> >> Those I believe are magic numbers for UFS superblocks... >> >>> So I was looking for something like: FS_ZFS_MAGIC >> >> ... so you won?t find that. >> >>> disklabel.h contains: >>> #ifdef FSTYPENAMES >>> static const char *fstypenames[] = { >>> >>> And further search: >>> /usr/include/sys/disk/bsd.h:#define FS_ZFS 27 /* Sun's ZFS */ >>> >>> Running: >>> #include "stdio.h" >>> >>> #include >>> #include >>> >>> int main() { >>> struct statfs fstr; >>> char * str; >>> >>> str = "/tmp"; >>> statfs(str, &fstr); >>> printf("%s, ftype: 0x%x.\n", str, fstr.f_type); >>> } >>> results in: >>> /tmp, ftype: 0xde. >>> >>> Now 0xde != 27, so the question is, where is this 0xde specified. >>> And more important is this f_type constant over all FreeBSD ZFS filesystems? >> >> You got me. And a quick look at sys/kern/vfs_syscalls.c doesn?t help except to imply that the type is set when the filesystem is mounted. I have no idea where 0xde comes from. > > Could that 0xde be the start of 0xdeadcode? > > 0xde is 222 decimal, that does not ring a bell for me either. Searching on 0xde did deliver indeed plenty 0xdeadc0de and sisters. the resulting size is 32bit, so if it is a leftover of 0xdeadcode, it is due to a not-32bit aligned access, since the 3 upper bytes are 0. Only way to find this out is dig thru the code. :) But I'm no hero at that. But there is atleast not a particular FS_ZFS_MAGIC!! And there is no obvious definition what is returned in f_type?? --WjW >>>>> struct statfs { >>>>> uint32_t f_version; /* structure version number */ >>>>> uint32_t f_type; /* type of filesystem */ >>>>> uint64_t f_flags; /* copy of mount exported flags */ >>>>> ...... >>>>> } >>>>> >>>>> Any hints where to look would be welcomed. >>>>> >>>>> Thanx, >>>>> --WjW >>>> -- >>>> Bob Bishop >>>> rb@gid.co.uk >> -- >> Bob Bishop t: +44 (0)118 940 1243 >> rb@gid.co.uk m: +44 (0)783 626 4518 >