public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Geir A. Myrestrand" <geir.myrestrand@falconstor.com>
To: xfs@oss.sgi.com
Cc: Eric Sandeen <sandeen@sandeen.net>
Subject: Re: New CentOS4/RHEL4-compatible xfs module rpms
Date: Thu, 07 Dec 2006 12:25:05 -0500	[thread overview]
Message-ID: <45784E71.4080605@falconstor.com> (raw)
In-Reply-To: <4560AB84.9060200@sandeen.net>

Eric Sandeen wrote:
> http://sandeen.net/rhel4_xfs/kernel-module-xfs-2.6.9-42.0.2.EL-0.2-1.src.rpm 
> 
> 
> rpmbuild --rebuild --target i686 
> kernel-module-xfs-2.6.9-42.0.2.EL-0.2-1.src.rpm
> 
> will build against the currently running kernel, or
> 
> rpmbuild --rebuild --target i686 --define "kernel_topdir 
> /lib/modules/2.6.9-42.0.2.EL/build" 
> kernel-module-xfs-2.6.9-42.0.2.EL-0.2-1.src.rpm
> 
> will build against what is defined in kernel_topdir
> 
> you need matching kernel & kernel-devel rpms installed to build.
> 

I built this for RHELAS4U2 x86_64 with the 2.6.9-22.ELsmp kernel.

I did enable the xfs_direct_io_locking.patch (see inside 
kernel-module-xfs.spec for details).

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.

Looks like xfs_io get stuck --see partial output from `ps auxf`:

strace -ff -o freeze.txt xfs_freeze -f /mnt/xfs
  \_ /bin/sh -f /usr/sbin/xfs_freeze -f /mnt/xfs
      \_ /usr/sbin/xfs_io -r -p xfs_freeze -x -c freeze /mnt/xfs

Anyone else encountering this issue?

-- 

Geir A. Myrestrand

  reply	other threads:[~2006-12-07 17:38 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 [this message]
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
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=45784E71.4080605@falconstor.com \
    --to=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