From: Ying-Hung Chen <ying@yingternet.com>
To: linux-xfs@oss.sgi.com
Cc: Ying-Hung Chen <ying@yingternet.com>
Subject: Re: xfs_repair xfsprogs version > 2.8.11
Date: Mon, 25 Dec 2006 17:59:20 +0800 [thread overview]
Message-ID: <458FA0F8.1020107@yingternet.com> (raw)
In-Reply-To: <458E643D.3090008@yingternet.com>
Hi there,
actually, i have trace the code in to xfs_repair/threads.c (taken from
2.8.18)
void
thread_init(void)
{
....
if ((status = pthread_attr_getstacksize(&attr, &stacksize)) != 0)
do_error(_("status from pthread_attr_getstacksize: %d"),
status);
stacksize *= 4;
if ((status = pthread_attr_setstacksize(&attr, stacksize)) != 0)
do_error(_("status from pthread_attr_setstacksize: %d"),
status);
....
}
the repair program dies in pthread_attr_setstacksize(&attr, stacksize)).
is there any reason why the program is trying to set the stacksize into
4 times the current size?
just for testing purposes, I remove the stacksize *= 4; the xfs_repair
seems to 'work', at least from user's point of view.
I have tested with x86 32bits machines with 2.4 and 2.6 kernels, they
both yield with the same results,
Thanks,
-Ying
Ying-Hung Chen wrote:
> Hi there,
>
> I found that xfs_repair always returns the following message with the
> xfsprogs version > 2.8.11
>
> [root@yroro i586]# xfs_repair /dev/hdb1
>
> fatal error -- status from pthread_attr_setstacksize: 22
>
> from the ChangeLog, seems like there is some internal changes with
> threads starting 2.8.11 .. the xfs_repair works for me up to 2.8.11, it
> fails to work on 2.8.16 and 2.8.18,
>
> how do I work around this problem?
>
> Thanks,
>
> -Ying
>
next prev parent reply other threads:[~2006-12-25 10:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-24 11:27 xfs_repair xfsprogs version > 2.8.11 Ying-Hung Chen
2006-12-25 9:59 ` Ying-Hung Chen [this message]
2006-12-28 10:21 ` David Chatterton
2006-12-29 1:51 ` Ying-Hung Chen
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=458FA0F8.1020107@yingternet.com \
--to=ying@yingternet.com \
--cc=linux-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