All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: "Lluís Batlle i Rossell" <viric@viric.name>
Cc: xfs@oss.sgi.com
Subject: Re: Volume fine on x86_64, corruption on ARM
Date: Sun, 03 Feb 2013 17:46:10 -0500	[thread overview]
Message-ID: <510EE8B2.6040301@redhat.com> (raw)
In-Reply-To: <20130127225258.GA2287@vicerveza.homeunix.net>

On 01/27/2013 05:52 PM, Lluís Batlle i Rossell wrote:
> Hello,
> 
> I'm using linux 3.7.3 in both machines (x86_64 and armv5tel), and I created
> a volume in x86_64 to be the rootfs for the ARM. All fine, until I plugged it
> into the ARM (Log below).
> 
> Given the corruption, I used xfs_repair in the x86_64, moved a lot of files into lost+found, plugged it back to the ARM, booted, and corruption again.
> 
> In the same USB HD, in the same ARM, and this same way, I've used succesfully
> ext4 and btrfs for a long time. Is there any known issue with ARM?
> 

FYI, I played around with my old sheevaplug a bit and so far, only
reproduced what I think are some USB (possibly hardware) issues. I
started with a 3.8.0-rc6 kernel and an sdcard and was reproducing
consistent USB resets leading to all sorts of errors.

I went back to 3.7.3 and replaced the sdcard with a thumb drive and
reproduced corruption errors several times on a reboot (not on initial
boot iirc). This required an fsck or reformat from my host system. I was
also occasionally reproducing USB debounce errors that required me to
power cycle and remove/attach the USB drive, which led me to try several
boot attempts with a clean power cycle and attaching the USB drive after
the bootloader (u-boot) has initialized, and with that sequence I
couldn't reproduce the error.

Unfortunately, I then tried several soft reboot cycles with the drive
attached and the error hasn't fired, so I can't make any serious
conclusion from that other than the possibility of flaky drivers or
hardware. Does your XFS rootfs _always_ fail, or can you get it to boot
occasionally or with a power cycle? This, of course, could be completely
unrelated to the issue you observe. I haven't tried a non-XFS filesystem
yet on this drive either. I'll play with it more when I have some more time.

Brian

> Thank you,
> Lluís.
> 
> ----------------------
> 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
> 
> [<c000ecd0>] (unwind_backtrace+0x0/0xfc) from [<c052d9c8>] (dump_stack+0x20/0x24)
> [<c052d9c8>] (dump_stack+0x20/0x24) from [<bf016690>] (xfs_error_report+0x64/0x70 [xfs])
> [<bf016690>] (xfs_error_report+0x64/0x70 [xfs]) from [<bf016700>] (xfs_corruption_error+0x64/0x80 [xfs])
> [<bf016700>] (xfs_corruption_error+0x64/0x80 [xfs]) from [<bf051a28>] (xfs_da_read_buf+0x1ac/0x27c [xfs])
> [<bf051a28>] (xfs_da_read_buf+0x1ac/0x27c [xfs]) from [<bf057e68>] (xfs_dir2_leaf_readbuf+0x220/0x5f0 [xfs])
> [<bf057e68>] (xfs_dir2_leaf_readbuf+0x220/0x5f0 [xfs]) from [<bf058784>] (xfs_dir2_leaf_getdents+0x12c/0x3ec [xfs])
> [<bf058784>] (xfs_dir2_leaf_getdents+0x12c/0x3ec [xfs]) from [<bf0545dc>] (xfs_readdir+0xf0/0x170 [xfs])
> [<bf0545dc>] (xfs_readdir+0xf0/0x170 [xfs]) from [<bf017cc8>] (xfs_file_readdir+0x58/0x68 [xfs])
> [<bf017cc8>] (xfs_file_readdir+0x58/0x68 [xfs]) from [<c00ff4a4>] (vfs_readdir+0x8c/0xb0)
> [<c00ff4a4>] (vfs_readdir+0x8c/0xb0) from [<c00ff618>] (sys_getdents64+0x78/0xd8)
> [<c00ff618>] (sys_getdents64+0x78/0xd8) from [<c0009340>] (ret_fast_syscall+0x0/0x2c)
> XFS (sda1): Corruption detected. Unmount and run xfs_repair
> 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
> 
> [<c000ecd0>] (unwind_backtrace+0x0/0xfc) from [<c052d9c8>] (dump_stack+0x20/0x24)
> [<c052d9c8>] (dump_stack+0x20/0x24) from [<bf016690>] (xfs_error_report+0x64/0x70 [xfs])
> [<bf016690>] (xfs_error_report+0x64/0x70 [xfs]) from [<bf016700>] (xfs_corruption_error+0x64/0x80 [xfs])
> [<bf016700>] (xfs_corruption_error+0x64/0x80 [xfs]) from [<bf051a28>] (xfs_da_read_buf+0x1ac/0x27c [xfs])
> [<bf051a28>] (xfs_da_read_buf+0x1ac/0x27c [xfs]) from [<bf057e68>] (xfs_dir2_leaf_readbuf+0x220/0x5f0 [xfs])
> [<bf057e68>] (xfs_dir2_leaf_readbuf+0x220/0x5f0 [xfs]) from [<bf058784>] (xfs_dir2_leaf_getdents+0x12c/0x3ec [xfs])
> [<bf058784>] (xfs_dir2_leaf_getdents+0x12c/0x3ec [xfs]) from [<bf0545dc>] (xfs_readdir+0xf0/0x170 [xfs])
> [<bf0545dc>] (xfs_readdir+0xf0/0x170 [xfs]) from [<bf017cc8>] (xfs_file_readdir+0x58/0x68 [xfs])
> [<bf017cc8>] (xfs_file_readdir+0x58/0x68 [xfs]) from [<c00ff4a4>] (vfs_readdir+0x8c/0xb0)
> [<c00ff4a4>] (vfs_readdir+0x8c/0xb0) from [<c00ff618>] (sys_getdents64+0x78/0xd8)
> [<c00ff618>] (sys_getdents64+0x78/0xd8) from [<c0009340>] (ret_fast_syscall+0x0/0x2c)
> XFS (sda1): Corruption detected. Unmount and run xfs_repair
> Failed to load default target: No such file or directory
> Trying to load rescue target...
> Failed to load rescue target: No such file or directory
> systemd-cgroups-agent[1324]: Failed to get D-Bus connection: Failed to connect to socket /org/freedesktop/systemd1/private: Connection refused
> 
> 
> 
> _______________________________________________
> 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

  parent reply	other threads:[~2013-02-03 22:48 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
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 [this message]
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=510EE8B2.6040301@redhat.com \
    --to=bfoster@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.