From: Eric Sandeen <sandeen@sandeen.net>
To: "Lluís Batlle i Rossell" <viric@viric.name>
Cc: Stan Hoeppner <stan@hardwarefreak.com>, xfs@oss.sgi.com
Subject: Re: Volume fine on x86_64, corruption on ARM
Date: Mon, 28 Jan 2013 11:10:45 -0600 [thread overview]
Message-ID: <5106B115.3080203@sandeen.net> (raw)
In-Reply-To: <20130128133759.GH2287@vicerveza.homeunix.net>
On 1/28/13 7:37 AM, Lluís Batlle i Rossell wrote:
> On Mon, Jan 28, 2013 at 04:46:57AM -0600, Stan Hoeppner wrote:
>> On 1/27/2013 4:52 PM, Lluís Batlle i Rossell wrote:
>>
>>> ----------------------
>>> starting systemd...
>>> systemd 197 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX +IMA +SYSVINIT -LIBCRYPTSETUP +GCRYPT +ACL +XZ)
>>>
>>> Welcome to NixOS 0.2pre-4eb2b09-af495e0!
>>>
>>> Failed to insert module 'autofs4'
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>> dea96000: 58 46 53 42 00 00 10 00 00 00 00 00 01 bd 26 f0 XFSB..........&.
>>> XFS (sda1): Internal error xfs_da_do_buf(2) at line 2192 of file fs/xfs/xfs_da_btree.c. Caller 0xbf057e68
>> ...
>> Your HDD is USB. Might the failure of this module to load have
>> something to do with the XFS problems?
I doubt it.
> I don't think it is related; the failure to load the module is because the
> module isn't there in my kernel. And that happens after the fs has been quite
> used in the boot, it's not mount time.
>
>> Forgive me if my lack of experience with this is causing me to ask a
>> stupid question. I've never used, nor will I ever use, XFS with a USB
>> drive.
>
> Well, I didn't expect it to be any trouble :) I've XFS in other USB drives, but
> before this, I only used them in x86_64. I might stop using XFS there.
It should work, and I'd like to find out why it's not. It used to. :)
But I'm a little low on time. Would you be willing to spot-check some older
kernels, and see if/when this regressed?
Thanks,
-Eric
> Thank you,
> Lluís.
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-01-28 17:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-27 22:52 Volume fine on x86_64, corruption on ARM Lluís Batlle i Rossell
2013-01-28 1:52 ` Eric Sandeen
2013-01-28 8:03 ` Lluís Batlle i Rossell
2013-01-28 10:46 ` Stan Hoeppner
2013-01-28 13:37 ` Lluís Batlle i Rossell
2013-01-28 17:10 ` Eric Sandeen [this message]
2013-01-28 22:37 ` Eric Sandeen
2013-01-28 22:40 ` Lluís Batlle i Rossell
2013-01-28 22:45 ` Eric Sandeen
2013-01-28 22:50 ` Lluís Batlle i Rossell
2013-01-29 5:21 ` Stan Hoeppner
2013-01-31 20:19 ` Phillip Lougher
2013-02-03 22:46 ` Brian Foster
2013-02-04 17:46 ` Lluís Batlle i Rossell
2013-02-27 14:51 ` Eric Sandeen
-- strict thread matches above, loose matches on Subject: below --
2014-02-15 3:18 Bill Webster
2014-02-16 22:21 ` Dave Chinner
2014-02-17 1:53 ` Stan Hoeppner
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=5106B115.3080203@sandeen.net \
--to=sandeen@sandeen.net \
--cc=stan@hardwarefreak.com \
--cc=viric@viric.name \
--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