From: "aluno3@poczta.onet.pl" <aluno3@poczta.onet.pl>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: xfs@oss.sgi.com
Subject: Re: Which xfsprogs version to which kernel version
Date: Thu, 26 Nov 2015 14:18:51 +0100 [thread overview]
Message-ID: <565706BB.3030006@poczta.onet.pl> (raw)
In-Reply-To: <20151126132638.53ed9fc7@harpe.intellique.com>
Yes I used -f option with 4.X version of xfsprogs but mounting the
volume was not possible - before mkfs.xfs finished successfully
(mkfs.xfs -f -m crc=0,finobt=0).
Should I stay in 3.1.X family of xfsprogs or is it recommended to use at
least 3.2.x version with kernel 3.10?
The most I care about xfs_repair.
On 11/26/15 13:26, Emmanuel Florac wrote:
> Le Thu, 26 Nov 2015 11:21:45 +0100
> "aluno3@poczta.onet.pl" <aluno3@poczta.onet.pl> écrivait:
>
>> mkfs.xfs -m crc=0,finobt=0
>>
>> but it does not work with 4.X version of xfsprogs. Call trace also
>> occurred so I tried to use 3.2.4 family with crc=0,finobt=0 and volume
>> mounted successfully.
>>
>
> Did you use -f? else mkfs.xfs won't do anything as it'll detect an
> existing filesystem.
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-11-26 13:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 10:21 Which xfsprogs version to which kernel version aluno3
2015-11-26 12:26 ` Emmanuel Florac
2015-11-26 13:18 ` aluno3 [this message]
2015-11-26 13:50 ` Brian Foster
2015-11-26 14:36 ` aluno3
2015-11-27 15:22 ` Brian Foster
2015-11-30 8:37 ` aluno3
2015-11-30 9:51 ` Carlos Maiolino
2015-11-30 21:41 ` Dave Chinner
2015-12-01 8:30 ` Martin Steigerwald
2015-12-01 20:26 ` Dave Chinner
2015-12-02 5:32 ` Eric Sandeen
2015-12-02 17:07 ` Arkadiusz Miśkiewicz
2015-12-02 21:14 ` Dave Chinner
2015-12-03 16:29 ` Eric Sandeen
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=565706BB.3030006@poczta.onet.pl \
--to=aluno3@poczta.onet.pl \
--cc=eflorac@intellique.com \
--cc=xfs@oss.sgi.com \
/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