From: Ryan Roh <unisist.roh@samsung.com>
To: 'Eric Sandeen' <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: RE: segmentation fault during mount
Date: Tue, 08 Feb 2011 14:12:01 +0900 [thread overview]
Message-ID: <030701cbc74e$b7f25680$27d70380$@samsung.com> (raw)
In-Reply-To: <4D50CA45.8070807@sandeen.net>
Dear Eric,
I don't know how I can make correct form to answer for this thread because
I'm newbie here. Sorry.
Anyway, this issue was happened from returned HDD from customer which was
used our PVR STB. And our STB has toggle power switch so I think user turned
off the power during recording something.
Thanks,
Ryan.
-----Original Message-----
From: Eric Sandeen [mailto:sandeen@sandeen.net]
Sent: Tuesday, February 08, 2011 1:45 PM
To: Ryan Roh
Cc: xfs@oss.sgi.com
Subject: Re: segmentation fault during mount
On 2/7/11 5:01 AM, Ryan Roh wrote:
> Dear Members,
>
> I'm using XFS based on STMicro SH4 based chip (STi7105).
>
> and I have some issue on xfs log mounting.
>
Were the errors after any sort of harsh testing of the filesystem, such as
usb disconnects or power off?
Or was this after a clean unmount?
-Eric
>
> 1. chip : sh4 STi7105
>
> 2. HDD : 320GB USB HDD USB 2.0 port.
>
> 3. OS : Linux 2.6.23.17 + patch for fixing cache aliasing issue.
>
> 4. XFSProgs version : 3.1.1
>
>
>
> mounting and repairing log in the below. This segmentation fault is
> caused by
>
> the assert in xfs_alloc_increment function of xfs_alloc_btree.c file.
> The btree
>
> level is equal to root level in the below code.
>
>
>
> /*
>
> * If we went off the root then we are seriously confused.
>
> */
>
> ASSERT(lev < cur->bc_nlevels);
>
>
...
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-02-08 5:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 11:01 segmentation fault during mount Ryan Roh
2011-02-08 4:44 ` Eric Sandeen
2011-02-08 5:12 ` Ryan Roh [this message]
2011-02-08 5:40 ` Eric Sandeen
2011-02-08 6:06 ` Ryan Roh
2011-02-08 15:00 ` 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='030701cbc74e$b7f25680$27d70380$@samsung.com' \
--to=unisist.roh@samsung.com \
--cc=sandeen@sandeen.net \
--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