From: "Janos Haar" <djani22@netcenter.hu>
To: "Nathan Scott" <nathans@sgi.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-xfs@oss.sgi.com>
Subject: Re: XFS related hang (was Re: How to send a break? - dump from frozen 64bit linux)
Date: Fri, 2 Jun 2006 00:14:04 +0200 [thread overview]
Message-ID: <01ed01c685c8$b46ec6f0$1800a8c0@dcccs> (raw)
In-Reply-To: 20060602075826.B530100@wobbly.melbourne.sgi.com
---- Original Message -----
From: "Nathan Scott" <nathans@sgi.com>
To: "Janos Haar" <djani22@netcenter.hu>
Cc: <linux-kernel@vger.kernel.org>; <linux-xfs@oss.sgi.com>
Sent: Thursday, June 01, 2006 11:58 PM
Subject: Re: XFS related hang (was Re: How to send a break? - dump from
frozen 64bit linux)
> On Wed, May 31, 2006 at 10:00:33AM +0200, Janos Haar wrote:
> >
> > Hey, i think i found something.
> > My quota on my huge device is broken.
> > (inferno -- 18014398504855404 0 0
18446744073709551519
> > 0 0)
>
> Hmm, that is interesting. I guess you don't know whether this
> accounting problem happened before you rebooted or whether it
> only just got this way (after journal recovery)?
In my system, this huge device is difficult.
I often need to reboot, and run xfs_repair, to make it clean. (nodes hangs,
reboots, etc...)
On the beginning, i use the xfs_repair without any options, but it requires
to do a mount/umount the mtp before.
The problem is, i often get an error message, (dump) during the journal
recovery, and after i cannot run the xfs_repair from script, because it
needs the log done by mount.
Now is my default reboot option is xfs_repair -L, so i dont know, this
happens before, or after, sorry.
>
> > I cant found a way to re-initialize it.
> > But anyway, at this point i dont need it, trying to disable the quota
usage.
> > We will see....
>
> Jan's recipe was spot on, do that.
The qouta stop solves the hangs problem.
This is a bug?
Cheers,
Janos
>
> cheers.
>
> --
> Nathan
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2006-06-01 22:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-27 12:58 How to send a break? Haar János
2006-05-27 23:43 ` Jim Crilly
2006-05-28 7:04 ` How to send a break? - dump from frozen 64bit linux Haar János
2006-05-28 16:17 ` Jesper Juhl
2006-05-28 17:34 ` Haar János
2006-05-29 4:37 ` Jesper Juhl
2007-08-20 7:44 ` Andev Debi
2006-05-30 10:22 ` Janos Haar
2006-05-30 19:03 ` Valdis.Kletnieks
2006-05-30 21:44 ` Janos Haar
2006-05-31 1:20 ` Steven Rostedt
2006-05-31 4:38 ` XFS related hang (was Re: How to send a break? - dump from frozen 64bit linux) Nathan Scott
2006-05-31 8:00 ` Janos Haar
2006-05-31 21:54 ` Jan Engelhardt
2006-06-01 7:29 ` Janos Haar
2006-06-01 9:44 ` Jan Engelhardt
2006-06-01 22:04 ` Nathan Scott
2006-06-02 5:11 ` Jan Engelhardt
2006-06-01 21:58 ` Nathan Scott
2006-06-01 22:14 ` Janos Haar [this message]
2006-06-01 23:43 ` Nathan Scott
2006-06-02 8:01 ` Janos Haar
2006-05-28 23:06 ` How to send a break? H. Peter Anvin
2006-05-29 15:08 ` linux-os (Dick Johnson)
2006-05-29 15:35 ` Valdis.Kletnieks
2006-05-29 17:32 ` Haar János
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='01ed01c685c8$b46ec6f0$1800a8c0@dcccs' \
--to=djani22@netcenter.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=nathans@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.