Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Robert Wyrick <rob@wyrick.org>, Anand Jain <anand.jain@oracle.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Next steps in recovery?
Date: Tue, 7 Sep 2021 12:53:42 +0800	[thread overview]
Message-ID: <362347bd-dca2-6074-c2c1-e453edd2a455@gmx.com> (raw)
In-Reply-To: <CAA_aC9-2ZA2+MOYbzMK+Sm_iwyPGCoaZYotJ0gShJURFv0-Xog@mail.gmail.com>



On 2021/9/7 下午12:36, Robert Wyrick wrote:
> What exactly would i be disabling?  I don't know what zoned does.

The zoned device support.

If you don't have any host-managed zoned device, there is no reason you
would like to enable it.

https://zonedstorage.io/introduction/

Thanks,
Qu

>
> On Mon, Sep 6, 2021, 9:07 PM Anand Jain <anand.jain@oracle.com> wrote:
>>
>> On 07/09/2021 10:36, Robert Wyrick wrote:
>>> Trying to build latest btrfs-progs.  I'm seeing errors in the configure script.
>>>
>>> $ cat /etc/os-release
>>> NAME="Linux Mint"
>>> VERSION="20.2 (Uma)"
>>> ID=linuxmint
>>> ID_LIKE=ubuntu
>>> PRETTY_NAME="Linux Mint 20.2"
>>> VERSION_ID="20.2"
>>> HOME_URL="https://www.linuxmint.com/"
>>> SUPPORT_URL="https://forums.linuxmint.com/"
>>> BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/"
>>> PRIVACY_POLICY_URL="https://www.linuxmint.com/"
>>> VERSION_CODENAME=uma
>>> UBUNTU_CODENAME=focal
>>>
>>> $ uname -a
>>> Linux bigbox 5.11.0-27-generic #29~20.04.1-Ubuntu SMP Wed Aug 11
>>> 15:58:17 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
>>>
>>> $ ./configure
>>> checking for gcc... gcc
>>> checking whether the C compiler works... yes
>>> checking for C compiler default output file name... a.out
>>> checking for suffix of executables...
>>> checking whether we are cross compiling... no
>>> checking for suffix of object files... o
>>> checking whether we are using the GNU C compiler... yes
>>> checking whether gcc accepts -g... yes
>>> checking for gcc option to accept ISO C89... none needed
>>> checking how to run the C preprocessor... gcc -E
>>> checking for grep that handles long lines and -e... /bin/grep
>>> checking for egrep... /bin/grep -E
>>> checking for ANSI C header files... yes
>>> checking for sys/types.h... yes
>>> checking for sys/stat.h... yes
>>> checking for stdlib.h... yes
>>> checking for string.h... yes
>>> checking for memory.h... yes
>>> checking for strings.h... yes
>>> checking for inttypes.h... yes
>>> checking for stdint.h... yes
>>> checking for unistd.h... yes
>>> checking minix/config.h usability... no
>>> checking minix/config.h presence... no
>>> checking for minix/config.h... no
>>> checking whether it is safe to define __EXTENSIONS__... yes
>>> checking for gcc... (cached) gcc
>>> checking whether we are using the GNU C compiler... (cached) yes
>>> checking whether gcc accepts -g... (cached) yes
>>> checking for gcc option to accept ISO C89... (cached) none needed
>>> checking whether C compiler accepts -std=gnu90... yes
>>> checking build system type... x86_64-pc-linux-gnu
>>> checking host system type... x86_64-pc-linux-gnu
>>> checking for an ANSI C-conforming const... yes
>>> checking for working volatile... yes
>>> checking whether byte ordering is bigendian... no
>>> checking for special C compiler options needed for large files... no
>>> checking for _FILE_OFFSET_BITS value needed for large files... no
>>> checking for a BSD-compatible install... /usr/bin/install -c
>>> checking whether ln -s works... yes
>>> checking for ar... ar
>>> checking for rm... /bin/rm
>>> checking for rmdir... /bin/rmdir
>>> checking for openat... yes
>>> checking for reallocarray... yes
>>> checking for clock_gettime... yes
>>> checking linux/perf_event.h usability... yes
>>> checking linux/perf_event.h presence... yes
>>> checking for linux/perf_event.h... yes
>>> checking linux/hw_breakpoint.h usability... yes
>>> checking linux/hw_breakpoint.h presence... yes
>>> checking for linux/hw_breakpoint.h... yes
>>> checking for pkg-config... /usr/bin/pkg-config
>>> checking pkg-config is at least version 0.9.0... yes
>>> checking execinfo.h usability... yes
>>> checking execinfo.h presence... yes
>>> checking for execinfo.h... yes
>>> checking for backtrace... yes
>>> checking for backtrace_symbols_fd... yes
>>> checking for xmlto... /usr/bin/xmlto
>>> checking for mv... /bin/mv
>>> checking for a sed that does not truncate output... /bin/sed
>>> checking for asciidoc... /usr/bin/asciidoc
>>> checking for asciidoctor... no
>>> checking for EXT2FS... yes
>>> checking for COM_ERR... yes
>>> checking for REISERFS... yes
>>> checking for FIEMAP_EXTENT_SHARED defined in linux/fiemap.h... yes
>>> checking for EXT4_EPOCH_MASK defined in ext2fs/ext2_fs.h... yes
>>> checking linux/blkzoned.h usability... yes
>>> checking linux/blkzoned.h presence... yes
>>> checking for linux/blkzoned.h... yes
>>> checking for struct blk_zone.capacity... no
>>> checking for BLKGETZONESZ defined in linux/blkzoned.h... yes
>>
>>> configure: error: linux/blkzoned.h does not provide blk_zone.capacity
>>
>>
>>>
>>> ---
>>>
>>> Info on the file in question (linux/blkzoned.h):
>>>
>>> $ dpkg -S /usr/include/linux/blkzoned.h
>>> linux-libc-dev:amd64: /usr/include/linux/blkzoned.h
>>>
>>> $ dpkg -l linux-libc-dev
>>> Desired=Unknown/Install/Remove/Purge/Hold
>>> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
>>> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
>>> ||/ Name                 Version      Architecture Description
>>> +++-====================-============-============-====================================
>>> ii  linux-libc-dev:amd64 5.4.0-81.91  amd64        Linux Kernel
>>> Headers for development
>>>
>>>
>>> So it appears that linux-libc-dev is way out-dated compared to my
>>> kernel.  I don't know how to update it, though... there doesn't appear
>>> to be a newer version available.
>>
>> You could disable the zoned.
>>
>>     ./configure --disable-zoned
>>
>>
>>
>>
>>

  reply	other threads:[~2021-09-07  4:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-03  2:43 Next steps in recovery? Robert Wyrick
2021-09-03  2:47 ` Robert Wyrick
2021-09-03  6:48 ` Qu Wenruo
2021-09-03  6:53   ` Qu Wenruo
     [not found]     ` <CAA_aC99-C8xOf7EAvJAMk2ZkYSaN2vyK7YFMw06utQ0T+tsh9A@mail.gmail.com>
2021-09-05 22:03       ` Qu Wenruo
2021-09-06 14:42         ` Robert Wyrick
2021-09-06 23:26           ` Qu Wenruo
2021-09-07  2:36             ` Robert Wyrick
2021-09-07  3:06               ` Anand Jain
2021-09-07  4:36                 ` Robert Wyrick
2021-09-07  4:53                   ` Qu Wenruo [this message]
2021-09-07 17:02                     ` Robert Wyrick
2021-09-07 17:17                       ` Robert Wyrick
2021-09-07 20:47                         ` Robert Wyrick
2021-09-07 23:17                           ` Qu Wenruo
2021-09-07 23:20                             ` Robert Wyrick
2021-09-07 23:28                               ` Qu Wenruo
2021-09-07 23:15                       ` Qu Wenruo
2021-09-08  1:59                         ` Su Yue
2021-09-08  6:50                           ` Robert Wyrick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=362347bd-dca2-6074-c2c1-e453edd2a455@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=anand.jain@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rob@wyrick.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox