All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Michlmayr <tbm@cyrius.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Tobias Frost <tobi@coldtobi.de>,
	linux-kernel@vger.kernel.org, debian-arm@lists.debian.org,
	xfs@oss.sgi.com
Subject: Re: XFS filesystem corruption on the arm(el) architecture
Date: Sat, 18 Oct 2008 10:57:56 +0200	[thread overview]
Message-ID: <20081018085752.GS25834@deprecation.cyrius.com> (raw)
In-Reply-To: <48F89E0F.6030307@sandeen.net>

* Eric Sandeen <sandeen@sandeen.net> [2008-10-17 09:15]:
> If you unmount & remount, does the ls work then?

I cannot even mount it:

debian:~# mkfs.xfs -f /dev/sda5
meta-data=/dev/sda5              isize=256    agcount=4, agsize=94380 blks
         =                       sectsz=512   attr=2
data     =                       bsize=4096   blocks=377519, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096
log      =internal log           bsize=4096   blocks=2560, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=0
realtime =none                   extsz=4096   blocks=0, rtextents=0
debian:~# mount /dev/sda5 /mnt
[42949596.920000] XFS mounting filesystem sda5
debian:~# cp /usr/bin/* /mnt/
debian:~# umount /mnt
debian:~# mount -t xfs /dev/sda5 /mnt
[42949612.290000] XFS mounting filesystem sda5
[42949612.460000] Starting XFS recovery on filesystem: sda5 (logdev: internal)
[42949612.480000] XFS: xlog_recover_process_data: bad flag
[42949612.500000] XFS: log mount/recovery failed: error 5
[42949612.500000] XFS: log mount failed
mount: /dev/sda5: can't read superblock
debian:~#

> Do you know what cachepolicy you're booted with?  If it's writeallocate,
> you might try cachepolicy=writeback, otherwise try cachepolicy=uncached
> (which will be horribly slow) and see if the problem goes away or not;
> it'd be a clue.

I just tried with cachepolicy=writeback and cachepolicy=uncached but I
get the same problem.
-- 
Martin Michlmayr
http://www.cyrius.com/

  reply	other threads:[~2008-10-18  8:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-01 20:38 XFS filesystem corruption on the arm(el) architecture Tobias Frost
2008-10-02  0:45 ` Dave Chinner
2008-10-02  0:56   ` Eric Sandeen
2008-10-02  1:17   ` Eric Sandeen
2008-10-16 21:25     ` Martin Michlmayr
2008-10-16 22:13       ` Eric Sandeen
2008-10-17  7:01         ` Martin Michlmayr
2008-10-17  9:46           ` Gaudenz Steinlin
2008-10-17 13:49             ` Eric Sandeen
2008-10-18 13:11             ` Tobias Frost
2008-10-18 19:48             ` Kirill A. Shutemov
2008-10-18 20:09               ` Christoph Hellwig
2008-10-18 20:17                 ` Kirill A. Shutemov
2008-10-17 14:15           ` Eric Sandeen
2008-10-18  8:57             ` Martin Michlmayr [this message]
2008-10-18 14:48               ` Eric Sandeen
2008-10-19  1:48               ` Dave Chinner
2008-10-19  3:06                 ` Eric Sandeen
2008-10-19  9:07                   ` Christoph Hellwig
2008-10-19 16:22                     ` Lennert Buytenhek
2008-10-19  5:12                 ` Martin Michlmayr
2008-10-02  1:42   ` 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=20081018085752.GS25834@deprecation.cyrius.com \
    --to=tbm@cyrius.com \
    --cc=debian-arm@lists.debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    --cc=tobi@coldtobi.de \
    --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.