mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Kleikamp <shaggy@austin.ibm.com>
To: caszonyi@yahoo.com (szonyi calin)
Cc: linux-kernel@vger.kernel.org,
	jfs-discussion@www-124.southbury.usf.ibm.com
Subject: Re: Jfs bug ?
Date: Tue, 28 Aug 2001 15:32:42 -0500 (CDT)	[thread overview]
Message-ID: <200108282032.f7SKWgZ18130@shaggy.austin.ibm.com> (raw)
In-Reply-To: <20010826151449.99510.qmail@web13108.mail.yahoo.com> from "szonyi calin" at Aug 26, 2001 08:14:49 AM

This should be discussed in jfs-discussion@www-124.ibm.com since
jfs is not included in either Linus' or Alan's kernels.

> Hi 
> I just formated one of mine linux partitions with jfs 
> I had the following problems
> 
> When restoring from backup
> 
> jfs_strtoUCS: char2uni returned -22.
> charset = iso8859-1, char = 0xffffff99
> jfs_strtoUCS: char2uni returned -22.
> charset = iso8859-1, char = 0xffffff99
> jfs_strtoUCS: char2uni returned -22.
> charset = iso8859-1, char = 0xffffff99
> jfs_strtoUCS: char2uni returned -22.
> charset = iso8859-1, char = 0xffffff99

First, char is simply "99", but it is being sign-extended.

A pathname in the backup has the character 0x99 which is
apparently not valid in the iso8859-1 codepage.  Can you tell
me what filesystem the backup was made from, and do you know
what codepage it used?  Currently, JFS uses whatever codepage
is compiled into the kernel as CONFIG_NLS_DEFAULT.  There
should probably be a mount flag that JFS uses to override this
value, but we don't have that yet.

Anyway, JFS probably substituted a "?" for the 0x99 in the
pathname, and created the file without any further problems.

I'm not sure about the hangs you described.  I'm currently
looking at some hangs that usually only occur under heavy
stress.  It would be useful to have a stack trace from the
hanging threads, especially the [jfsCommit] thread.

-- 
David Kleikamp
IBM Linux Technology Center

      reply	other threads:[~2001-08-28 20:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-26 15:14 szonyi calin
2001-08-28 20:32 ` Dave Kleikamp [this message]

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=200108282032.f7SKWgZ18130@shaggy.austin.ibm.com \
    --to=shaggy@austin.ibm.com \
    --cc=caszonyi@yahoo.com \
    --cc=jfs-discussion@www-124.southbury.usf.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®