From: Karl Schmidt <karl@xtronics.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: Ben Hutchings <ben@decadent.org.uk>,
714974@bugs.debian.org, jfs-discussion@lists.sourceforge.net,
Jonathan McDowell <noodles@earth.li>,
linux-nfs@vger.kernel.org
Subject: Re: [Jfs-discussion] NFS 'readdir loop' error on JFS
Date: Sat, 10 Aug 2013 14:43:24 -0500 [thread overview]
Message-ID: <520697DC.1030500@xtronics.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1308092352550.7081@trent.utfs.org>
On 08/10/2013 02:28 AM, Christian Kujau wrote:
> Interesting stuff. Out of curiosity I just tried this myself, both client
> & server are virtual machines running Debian/stable (3.2.0-4-amd64) and I
> was able to reproduce this. A test case would be:
>
I still haven't rebooted that machine - last chance to ask for any test info - as it looks like you
have a test case anyway.
I haven't lost any data that I know of - just programs complaining etc.
IMO, at one time, jfs was really a better choice ( good set of tools). Even in a few cases where
hardware failed the jfs tools worked well. Today with everyone banging on ext4 it has become the
better choice. ( I don't think IBM is interested in supporting jfs - no idea if they are phasing out
jfs2? ).
--------------------------------------------------------------------------------
Karl Schmidt EMail Karl@xtronics.com
Transtronics, Inc. WEB http://secure.transtronics.com
3209 West 9th Street Ph (785) 841-3089
Lawrence, KS 66049 FAX (785) 841-0434
The world runs on individuals pursuing their separate interests.
The great achievements of civilization have not come from
government bureaus. Einstein didn’t construct his theory under
order from a bureaucrat. Henry Ford didn’t revolutionize the
automobile industry that way.
--------------------------------------------------------------------------------
next prev parent reply other threads:[~2013-08-10 19:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 1:13 NFS 'readdir loop' error on JFS Ben Hutchings
2013-07-08 14:02 ` bjschuma
2013-07-08 15:43 ` Karl Schmidt
2013-08-09 20:44 ` Karl Schmidt
2013-08-10 7:28 ` [Jfs-discussion] " Christian Kujau
2013-08-10 19:43 ` Karl Schmidt [this message]
2013-08-12 8:18 ` Christian Kujau
2013-08-12 8:29 ` Christian Kujau
2013-08-12 16:29 ` J. Bruce Fields
2013-08-12 20:04 ` Christian Kujau
2013-08-15 3:54 ` [PATCH] jfs: avoid misuse of cookie value of 2 Dave Kleikamp
2013-08-15 4:29 ` Christian Kujau
2013-08-15 7:09 ` Christian Kujau
2013-08-15 13:38 ` Dave Kleikamp
2013-08-15 20:48 ` [PATCH] jfs: fix readdir cookie incompatibility with NFSv4 Dave Kleikamp
2013-08-15 21:26 ` Christian Kujau
2013-08-15 22:09 ` Dave Kleikamp
2013-08-17 20:01 ` Ben Hutchings
2013-08-19 19:11 ` [JunkMail] " ben
2013-08-29 22:48 ` Jonathan McDowell
2013-09-05 3:40 ` Bug#714974: " Jonathan McDowell
2013-08-24 22:21 ` [Jfs-discussion] " Christian Kujau
2013-08-26 22:27 ` Dave Kleikamp
2013-08-15 13:38 ` [PATCH] jfs: avoid misuse of cookie value of 2 J. Bruce Fields
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=520697DC.1030500@xtronics.com \
--to=karl@xtronics.com \
--cc=714974@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-nfs@vger.kernel.org \
--cc=lists@nerdbynature.de \
--cc=noodles@earth.li \
/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.