public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Scott <nscott@aconex.com>
To: geir.myrestrand@falconstor.com
Cc: xfs@oss.sgi.com, Eric Sandeen <sandeen@sandeen.net>
Subject: Re: New CentOS4/RHEL4-compatible xfs module rpms
Date: Fri, 08 Dec 2006 08:11:46 +1100	[thread overview]
Message-ID: <1165525906.30459.25.camel@edge> (raw)
In-Reply-To: <45787ED4.5070801@falconstor.com>

On Thu, 2006-12-07 at 15:51 -0500, Geir A. Myrestrand wrote:
> Eric Sandeen wrote:
> > Geir A. Myrestrand wrote:
> > 
> >> However, I run into issues with xfs_freeze as it often locks up when I 
> >> try to freeze a file system where there is I/O activity. Sometimes it 
> >> happen on the first xfs_freeze invocation to freeze the file system, 
> >> other times I have to unfreeze and then it happens on the second time I 
> >> freeze. xfs_freeze never returns when this happens.
> >>
> > 
> > Did you have this problem on the previous version?
> 
> I just tested with the old version, and I run into the same issue.
> 

Does it happen with mainline (current) kernels?  This is ringing some
distant bells, something to do with an atomic_inc being in the wrong
spot in [_]xfs_trans_alloc ... or maybe a wrong call to xfs_trans_alloc
instead of the '_' prefixed version - details are murky now though.  I
do remember fixing ... something in here, a few months back, that fix
may not be in Eric's codebase yet.

cheers.

-- 
Nathan

  reply	other threads:[~2006-12-07 21:12 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-19 19:07 New CentOS4/RHEL4-compatible xfs module rpms Eric Sandeen
2006-12-07 17:25 ` Geir A. Myrestrand
2006-12-07 17:52   ` Eric Sandeen
2006-12-07 18:17     ` Geir A. Myrestrand
2006-12-07 23:26       ` David Chinner
2006-12-08  2:58         ` Geir A. Myrestrand
2006-12-07 18:19     ` Geir A. Myrestrand
2006-12-07 20:51     ` Geir A. Myrestrand
2006-12-07 21:11       ` Nathan Scott [this message]
2006-12-07 21:35         ` Geir A. Myrestrand
2006-12-07 21:40           ` Nathan Scott
2006-12-07 21:51             ` Geir A. Myrestrand
2006-12-07 22:06               ` Nathan Scott
2006-12-07 22:16                 ` Geir A. Myrestrand
2006-12-07 22:18                   ` Eric Sandeen
2006-12-07 22:25                     ` Geir A. Myrestrand
2006-12-07 22:30                       ` Eric Sandeen
2006-12-07 22:52                         ` Geir A. Myrestrand
2006-12-07 22:53                           ` Eric Sandeen
2006-12-07 23:08                             ` Geir A. Myrestrand
2007-07-19 14:37 ` James Braid
2007-07-19 15:15   ` Eric Sandeen
2007-07-21  3:34     ` James Braid
2007-07-21 14:58       ` Eric Sandeen
2007-07-21 15:36         ` James Braid
  -- strict thread matches above, loose matches on Subject: below --
2007-08-08 16:04 James Pearson
2007-08-08 16:09 ` 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=1165525906.30459.25.camel@edge \
    --to=nscott@aconex.com \
    --cc=geir.myrestrand@falconstor.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