Journaled File System

Hi.

There's a big problem booting Linux since jfs didn't get unmounted
correctly yesterday: the filesystem doesn't getting recognized anymore
as jfs but as msdos filesystem instead.

Is there a way to repair that? I already tried booting the gentoo
installation cd and doing a "jfs_fsck -a /dev/hdg1", but no errors are
found. The 1st time I called this command, the transaction log was being
replayed, but this didn't change anything related to my problem.

When booting the gentoo install cd, I can mount /dev/hdg1, but I have to
specify "-t jfs" as parameter. mount doesn't auto-recognize jfs, too!
Well, at least all my data is still there.

Any suggestions?

Bye.
Thorsten
-- 
PGP public key:
http://home.arcor.de/thorstenhirsch/thirschatwebde.asc

I'm seeing a strange behaviour with symlinks, and I'm unable to understand if 
this is due to jfs, ext3, or something else, so I'm asking here, please be 
patient :)

Situation:

/dev/hda5 on / type jfs (rw)
/dev/hda1 on /boot type ext2 (rw)
/dev/hda7 on /home type ext3 (rw)
/dev/sda5 on /archivio type jfs (rw,iocharset=iso8859-15)

(sda5 is a serial ata device)

On my home (/dev/hda1/)I've a symlink pointing to a directory located 
on /dev/sda5 :
lrwxrwxrwx  1 cova cova 18 feb 10 23:57 src -> /archivio/cova/src/

If I cd to that directory from my home, then is impossible to refer a file 
using relative path when .. leads to cross the symlink. Example:

[cova@... linux-2.6.5-rc2-mm1]$ pwd
/home/cova/src/linux-2.6.5-rc2-mm1
(here I'm in /dev/sda5 device)
[cova@... linux-2.6.5-rc2-mm1]$ ls -la ../linux-2.6.5-rc2-mm4/README
-rw-r--r--  1 cova cova 13976 mar 11 03:55 ../linux-2.6.5-rc2-mm4/README

(this is OK, the README is on the same FS).

Now I try with a file on other FS:
[cova@... linux-2.6.5-rc2-mm1]$ ls 
-la ../../store/soft/linux/udev-021-1.src.rpm
ls: ../../store/soft/linux/udev-021-1.src.rpm: No such file or directory

BUT:
[cova@... linux-2.6.5-rc2-mm1]$ ls 
-la /home/cova/store/soft/linux/udev-021-1.src.rpm
-rw-rw-r--  1 cova cova 384905 mar  3 
23:48 /home/cova/store/soft/linux/udev-021-1.src.rpm

(store/ dir is on /dev/hda7 FS)

I'm a little bit puzzled by this behaviour; to add more information, if I use 
tab completation when writing "ls 
-la ../../store/soft/linux/udev-021-1.src.rpm" command line, the bash 
completes correctly the filenames, even udev-021-1.src.rpm, so the file 
exists, but completes the directory names (store, soft and linux) placing a 
space and not a slash after the name, so it's that the name is interpreted as 
filename and not dirname.

Is this the expected behaviour? I'm doing something wrong? Is an ext3,jfs, or 
linux VFS issue?

Many thanks for any help.


-- 
Fabio Coatti       http://www.ferrara.linux.it/members/cova     
Ferrara Linux Users Group           http://ferrara.linux.it
GnuPG fp:9765 A5B6 6843 17BC A646  BE8C FA56 373A 5374 C703
Old SysOps never die... they simply forget their password.

Hi,

i ran into a strange but serious problem when my raid restartet after a =
short power loss.
i am using a 3ware raid controller. the device it provides is /dev/sdb =
(the raid5 partition)

i am using 2.4.21 linux kernel with the build in jfs and 3ware drivers

doing a lowlevel check of the raid5 with the 3ware tools confirms =
integrity and functionality of the raid itself.

on /dev/sdb is a jfs

after the powerloss "mount /dev/sdb /mnt" tells me:

    host:~# mount /dev/sdb /mnt
    mount: wrong fs type, bad option, bad superblock on /dev/sdb,
           or too many mounted file systems
           (aren't you trying to mount an extended partition,
           instead of some logical partition inside?)

"mount -t jfs /dev/sdb /mnt" tells the same thing.

the device does exist:

host:~# cat /proc/partitions
major minor  #blocks  name     rio rmerge rsect ruse wio wmerge wsect =
wuse running use aveq

   8     0   17921835 sda 1478 3173 37028 7840 865 221 8794 25100 0 8710 =
32940
   8     1      32098 sda1 6 18 48 30 1 0 2 0 0 30 30
   8     2     996030 sda2 1 0 8 10 0 0 0 0 0 10 10
   8     3   16892347 sda3 1470 3152 36964 7790 864 221 8792 25100 0 =
8670 32890
   8    16 1715814464 sdb 56982 344926 3214952 446240 0 0 0 0 0 432040 =
446220


my first action was doing a read-only check with the jfs-utils:

    host:~# jfs_fsck -v -n /dev/sdb
    jfs_fsck version 1.1.4, 30-Oct-2003
    processing started: 3/26/2004 14.32.21
    The current device is:  /dev/sdb
    Open(...READONLY...) returned rc =3D 0
    Primary superblock is valid.
    The type of file system for the device is JFS.
    Block size in bytes:  4096
    Filesystem size in blocks:  428953616
    **Phase 1 - Check Blocks, Files/Directories, and  Directory Entries
    **Phase 2 - Count links
    **Phase 3 - Duplicate Block Rescan and Directory Connectedness
    **Phase 4 - Report Problems
    **Phase 5 - Check Connectivity
    **Phase 6 - Perform Approved Corrections
    **Phase 7 - Verify File/Directory Allocation Maps
    **Phase 8 - Verify Disk Allocation Maps
    Filesystem Summary:
    Blocks in use for inodes:  94568
    Inode count:  756544
    File count:  700866
    Directory count:  37027
    Block count:  428953616
    Free block count:  81007537
    1715814464 kilobytes total disk space.
       158237 kilobytes in 37027 directories.
    1391320657 kilobytes in 700866 user files.
            0 kilobytes in extended attributes
            0 kilobytes in access control lists
       621896 kilobytes reserved for system use.
    324030148 kilobytes are available for use.
    File system checked READ ONLY.
    Filesystem is clean.
    processing terminated:  3/26/2004 14:40:28  with return code: 0  =
exit code: 0.

after some looking around i found that "jfs_tune -l /dev/sdb" tells me:

    host:~# jfs_tune -l /dev/sdb
    jfs_tune version 1.1.4, 30-Oct-2003

    JFS filesystem superblock:

    JFS magic number:       'JFS1'
    JFS version:            1
    JFS state:              mounted
    JFS flags:              JFS_LINUX  JFS_COMMIT  JFS_GROUPCOMMIT  =
JFS_INLINELOG
    Aggregate block size:   4096 bytes
    Aggregate size:         3431458256 blocks
    Physical block size:    512 bytes
    Allocation group size:  4194304 aggregate blocks
    Log device number:      0x810
    Filesystem creation:    Fri Oct 17 02:18:13 2003
    Volume label:           'STORAGE'

maybe the problem is that the jfs on /dev/sdb still "thinks" it is =
mounted?
because of the "JFS state: mounted"?

if that might be the reason, is there any way to reset the state to "not =
mounted" or whatever it might should be?

or if anybody else encounterd the same problem. how do i get rid of it??

there is lots of data on that raid which is (as usual of course) vital =
to me...
it looks like there is still hope.

Please help?


Regards,

Henk Birkholz
Bremen / Germany

I have a 200GB external hard disc for backups. I try to find a capable
filesystem for it and it should be used for a long time...

I used ext2 for now 8 years and ext3 on my thinkpad for about 1 year. I
haven't any error since I used those FS so far. (or I never saw, that I
have a problem)

I just tried ext3, reiserfs and now jfs. Benchmark performance ins't important for
me in the first place. I need a reliable FS with journaling support and low overhead used
for the filesystem structure.

I had a "not so" good feeling with reiser (please don't flame). I found
that ext2/3 used a lot of space for its static inode allocation.

Are there any serious problems or possibility of data loss if I use JFS
?

Best regards
Marcel

---------- Início da mensagem original -----------

      De: jfs-discussion-admin@...
    Para: jfs-discussion@...
      Cc: 
    Data: Thu, 25 Mar 2004 12:02:01 -0500
 Assunto: Jfs-discussion digest, Vol 1 #498 - 4 msgs

> Send Jfs-discussion mailing list submissions to
> 	jfs-discussion@...
> 
> To subscribe or unsubscribe via the World Wide Web, 
visit
> 	http://www-
124.ibm.com/developerworks/oss/mailman/listinfo/jfs-
discussion
> 
> or, via email, send a message with subject or 
body 'help' to
> 	jfs-discussion-request@...
> 
> You can reach the person managing the list at
> 	jfs-discussion-admin@...
> 
> When replying, please edit your Subject line so it is 
more specific
> than "Re: Contents of Jfs-discussion digest..."
> 
> 
> Today's Topics:
> 
>    1. Re: kernel 2.6.4: Bug in JFS file system? 
(Andreas Theofilu)
>    2. [Fwd: Re: [Jfs-discussion] (no subject)] (Dave 
Kleikamp)
>    3. Re: (no subject) (Dave Kleikamp)
>    4. Re: kernel 2.6.4: Bug in JFS file system? (Dave 
Kleikamp)
> 
> --__--__--
> 
> Message: 1
> Date: Wed, 24 Mar 2004 19:59:52 +0100
> From: Andreas Theofilu <abfall@...>
> To: Dave Kleikamp <shaggy@...>
> Cc: linux-kernel@..., jfs-discussion@...
126.southbury.usf.ibm.com
> Organization: Theos Soft
> Subject: [Jfs-discussion] Re: kernel 2.6.4: Bug in 
JFS file system?
> 
> On Wed, 24 Mar 2004 07:45:17 -0600
> Dave Kleikamp <shaggy@...> wrote:
> 
> > Unfortunately, existing files with a non-zero high 
byte in a character
> > are no longer accessible.  jfs should have printed 
a syslog message
> > recommending that the file system be mounted with 
iocharset=utf8 to
> > access the file.
> > 
> Thanks for that information. I didn't found any 
syslog message, but
> mounting the partition with iocharset=utf8 brought 
back the previous
> unaccessible files.Now everything is working fine 
again.
> 
> -- 
> Andreas Theofilu
> http://www.TheosSoft.net/
> 
>                      --==| Enjoy the science of 
Linux! |==--
> 
> --__--__--
> 
> Message: 2
> Subject: [Fwd: Re: [Jfs-discussion] (no subject)]
> From: Dave Kleikamp <shaggy@...>
> To: Domenico Di Tullio <domenico.di-tullio@...>
> Cc: JFS Discussion <jfs-discussion@...
126.southbury.usf.ibm.com>
> Date: Wed, 24 Mar 2004 14:10:20 -0600
> 
> I'm resending this since I didn't see it appear on 
the jfs-discussion
> list.  Did you receive the original reply, Domenico?
> 
> -----Forwarded Message-----
> From: Dave Kleikamp <shaggy@...>
> To: Domenico Di Tullio <domenico.di-tullio@...>
> Cc: JFS Discussion <jfs-discussion@...
124.southbury.usf.ibm.com>
> Subject: Re: [Jfs-discussion] (no subject)
> Date: Wed, 24 Mar 2004 09:06:53 -0600
> 
> On Wed, 2004-03-24 at 08:49, Domenico Di Tullio wrote:
> > Hello,
> > 
> > I would to know for the jfs file system the follows 
characteristics :
> 
> > - max total number of files;
> This is limited by the 32-bit inode number, so just 
under 4G.
> 
> > -max total number of directories;
> again just under 4G.  files + directories < 4G.
> 
> > -max number of files per directories;
> just under 4G.  I think it might be 4G-3, but I'm not 
exactly sure.
> 
> > -max file size;
> 2^52, or 4 Petabytes.  blocksize = 4K, and jfs used 
40 bits to store the
> block number.  This also limits the file system size 
on 64-bit systems.
> 
> > -max number of simultaneously opened files.
> jfs has no limit.  I'm not sure what limits this in 
the vfs.
> -- 
> David Kleikamp
> IBM Linux Technology Center
> 
> 
> --__--__--
> 
> Message: 3
> Subject: Re: [Jfs-discussion] (no subject)
> From: Dave Kleikamp <shaggy@...>
> To: Domenico Di Tullio <domenico.di-tullio@...>
> Cc: JFS Discussion <jfs-discussion@...
126.southbury.usf.ibm.com>
> Date: Wed, 24 Mar 2004 09:06:53 -0600
> 
> On Wed, 2004-03-24 at 08:49, Domenico Di Tullio wrote:
> > Hello,
> > 
> > I would to know for the jfs file system the follows 
charateristics :
> 
> > - max total number of files;
> This is limited by the 32-bit inode number, so just 
under 4G.
> 
> > -max total number of directories;
> again just under 4G.  files + directories < 4G.
> 
> > -max number of files per directories;
> just under 4G.  I think it might be 4G-3, but I'm not 
exactly sure.
> 
> > -max file size;
> 2^52, or 4 Petabytes.  blocksize = 4K, and jfs used 
40 bits to store the
> block number.  This also limits the file system size 
on 64-bit systems.
> 
> > -max number of simultaneously opened files.
> jfs has no limit.  I'm not sure what limits this in 
the vfs.
> 
> -- 
> David Kleikamp
> IBM Linux Technology Center
> 
> 
> --__--__--
> 
> Message: 4
> From: Dave Kleikamp <shaggy@...>
> To: Andreas Theofilu <andreas@...>
> Cc: linux-kernel <linux-kernel@...>,
>    JFS Discussion <jfs-discussion@...
126.southbury.usf.ibm.com>
> Date: Wed, 24 Mar 2004 07:45:17 -0600
> Subject: [Jfs-discussion] Re: kernel 2.6.4: Bug in 
JFS file system?
> 
> On Tue, 2004-03-23 at 12:55, Andreas Theofilu wrote:
> > Hi to all,
> > 
> > Since kernel 2.6.4 I'm not able to access files 
with a special character
> > in the file name, such as the german umlaute. Every 
attempt to access such
> > a file gives me the error: cannot stat file
> 
> I did this to you.  I changed jfs's default character 
translation
> behavior.  jfs stores the file names in ucs-16.  It 
had used the
> character set defined by CONFIG_NLS_DEFAULT to 
determine how to
> translate to or from ucs-16.  This can be overridden 
with the iocharset=
> mount option.
> 
> After many complaints about characters that were 
being rejected by jfs,
> and after getting as much feedback as I was able to 
obtain, I changed
> the default behavior so that no translation is done.  
Each byte of the
> file name is now stored in the lower byte of the ucs-
16 character. 
> (This is equivalent to iocharset=iso8859-1, which is 
the default value
> of CONFIG_NLS_DEFAULT.)
> 
> Unfortunately, existing files with a non-zero high 
byte in a character
> are no longer accessible.  jfs should have printed a 
syslog message
> recommending that the file system be mounted with 
iocharset=utf8 to
> access the file.
> 
> > I'm using several partitions with JFS file system 
and had never seen such
> > a strange behavior before. The relevant kernel 
settings are at the bottom
> > of the mail.
> > 
> > I already unmounted the partition and run fsck on 
it (fsck.jfs -f
> > /dev/hda8), but it told me that everything is ok 
and I'm still not able to
> > access this files. Also a reboot of the machine 
didn't change anything. I
> > booted 2.6.3 again and renamed the files in 
question (no more special
> > characters in the file name). Now I can access 
these files with 2.6.4
> > also.
> 
> Another alternative would have been to mount the 
filesystem with "-o
> iocharset=<charset>" where <charset> is the value of
> CONFIG_NLS_DEFAULT.  To make that behavior permanent, 
you can add the
> iocharset= flag to /etc/fstab.
> 
> > Although I'm a programmer, I'm not a kernel hacker 
and don't know where
> > to start looking for this problem. Could anybody 
give me a hint where to
> > start looking?
> 
> I'm sorry this caused you problems.  I knew making 
this change would
> cause some confusion, but I think in the long run, 
jfs is better off
> with a more predictable default behavior.
> 
> -- 
> David Kleikamp
> IBM Linux Technology Center
> 
> 
> 
> --__--__--
> 
> _______________________________________________
> Jfs-discussion mailing list
> Jfs-discussion@...
> http://www-
124.ibm.com/developerworks/oss/mailman/listinfo/jfs-
discussion
> 
> 
> End of Jfs-discussion Digest
> 
 
__________________________________________________________________________
Acabe com aquelas janelinhas que pulam na sua tela.
AntiPop-up UOL - É grátis!
http://antipopup.uol.com.br/

On Wed, 24 Mar 2004 07:45:17 -0600
Dave Kleikamp <shaggy@...> wrote:

> Unfortunately, existing files with a non-zero high byte in a character
> are no longer accessible.  jfs should have printed a syslog message
> recommending that the file system be mounted with iocharset=utf8 to
> access the file.
> 
Thanks for that information. I didn't found any syslog message, but
mounting the partition with iocharset=utf8 brought back the previous
unaccessible files.Now everything is working fine again.

-- 
Andreas Theofilu
http://www.TheosSoft.net/

                     --==| Enjoy the science of Linux! |==--

Hello,

I would to know for the jfs file system the follows charateristics :
- max total number of files;
-max total number of directories;
-max number of files per directories;
-max file size;
-max number of simultaneously opened files.

Thanks

I'm resending this since I didn't see it appear on the jfs-discussion
list.  Did you receive the original reply, Domenico?

-----Forwarded Message-----
From: Dave Kleikamp <shaggy@...>
To: Domenico Di Tullio <domenico.di-tullio@...>
Cc: JFS Discussion <jfs-discussion@...>
Subject: Re: [Jfs-discussion] (no subject)
Date: Wed, 24 Mar 2004 09:06:53 -0600

On Wed, 2004-03-24 at 08:49, Domenico Di Tullio wrote:
> Hello,
> 
> I would to know for the jfs file system the follows characteristics :

> - max total number of files;
This is limited by the 32-bit inode number, so just under 4G.

> -max total number of directories;
again just under 4G.  files + directories < 4G.

> -max number of files per directories;
just under 4G.  I think it might be 4G-3, but I'm not exactly sure.

> -max file size;
2^52, or 4 Petabytes.  blocksize = 4K, and jfs used 40 bits to store the
block number.  This also limits the file system size on 64-bit systems.

> -max number of simultaneously opened files.
jfs has no limit.  I'm not sure what limits this in the vfs.
-- 
David Kleikamp
IBM Linux Technology Center

Begin forwarded message:

Date: Tue, 23 Mar 2004 19:55:29 +0100
From: Andreas Theofilu <andreas@...>
To: linux-kernel <linux-kernel@...>
Subject: kernel 2.6.4: Bug in JFS file system?


Hi to all,

Since kernel 2.6.4 I'm not able to access files with a special character
in the file name, such as the german umlaute. Every attempt to access such
a file gives me the error: cannot stat file

I'm using several partitions with JFS file system and had never seen such
a strange behavior before. The relevant kernel settings are at the bottom
of the mail.

I already unmounted the partition and run fsck on it (fsck.jfs -f
/dev/hda8), but it told me that everything is ok and I'm still not able to
access this files. Also a reboot of the machine didn't change anything. I
booted 2.6.3 again and renamed the files in question (no more special
characters in the file name). Now I can access these files with 2.6.4
also.

Allthough I'm a programmer, I'm not a kernel hacker and don't know where
to start looking for this problem. Could anybody give me a hint where to
start looking?

-------------------------
Kernel 2.6.4 settings (.config)
#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
CONFIG_JFS_FS=y
CONFIG_JFS_POSIX_ACL=y
# CONFIG_JFS_DEBUG is not set
CONFIG_JFS_STATISTICS=y
CONFIG_FS_POSIX_ACL=y
# CONFIG_XFS_FS is not set
CONFIG_MINIX_FS=y
# CONFIG_ROMFS_FS is not set
CONFIG_QUOTA=y
# CONFIG_QFMT_V1 is not set
CONFIG_QFMT_V2=y
CONFIG_QUOTACTL=y
CONFIG_AUTOFS_FS=y
CONFIG_AUTOFS4_FS=y

-- 
Andreas Theofilu
http://www.TheosSoft.net/

                     --==| Enjoy the science of Linux! |==--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Dear jfs developers.
I used lastest jfs(1.1.4) with linux-2.4.18 to Arm based machine.

Deleting files, JFS is corrupted with below Oops message.


Program received signal SIGSEGV, Segmentation fault.

txLog (log=0xc3c15380, tblk=0xc4000150, cd=0xc3c5be9c) at
jfs_txnmgr.c:1338

lrd->log.redopage.fileset = cpu_to_le32(JFS_IP(ip)->fileset);


and 

 

Program received signal SIGSEGV, Segmentation fault.

0xc00c5380 in remove_from_hash (mp=0xc03f0108, hash_ptr=0xc03f8000)

    at jfs_metapage.c:258

258                     assert(*hash_ptr == mp);


I guess something wrong on the log structure. I have tried to make it
but failed.

So, I have no idea.

May I ask what is the problem and how can I fix that?

Or there are anybody using jfs with ARM machine?

Thank you for your kind reading and Have a nice day.


-----Original Message-----
From: jfs-discussion-admin@... [mailto:jfs-discussion-
admin@...] On Behalf Of jfs-discussion-request@...
124.ibm.com
Sent: Wednesday, March 10, 2004 2:02 AM
To: jfs-discussion@...
Subject: Jfs-discussion digest, Vol 1 #495 - 9 msgs

Send Jfs-discussion mailing list submissions to
	jfs-discussion@...

To subscribe or unsubscribe via the World Wide Web, visit
	http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-
discussion

or, via email, send a message with subject or body 'help' to
	jfs-discussion-request@...

You can reach the person managing the list at
	jfs-discussion-admin@...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Jfs-discussion digest..."


Today's Topics:

   1. Re: jfs does not mount (Zeno R.R. Davatz)
   2. Re: jfs does not mount (Zeno R.R. Davatz)
   3. Phase 7 Errors detected in Fileset File/Directory Allocation Map
       control information (Zeno R.R. Davatz)
   4. Re: Phase 7 Errors detected in Fileset File/Directory Allocation
Map control information (Per Jessen)
   5. Re: Phase 7 Errors detected in Fileset
       File/Directory Allocation Map control information (Dave Kleikamp)
   6. Re: Phase 7 Errors detected in Fileset
       File/Directory Allocation Map control information (Zeno R.R.
Davatz)

--__--__--

Message: 1
Date: Tue, 9 Mar 2004 10:07:32 +0100
From: "Zeno R.R. Davatz" <zdavatz@...>
To: "jfs-discussion@..."
 <jfs-discussion@...>
Subject: Re: [Jfs-discussion] jfs does not mount
Organization: ywesee - intellectual capital connected

Hi 

Thanks for all the kind replys.

I downloaded the latest gentoo-Universal CD. 

When I do mount /dev/hda3 /mnt/gentoo I get:
jfs_mount: Mount Failure: File System Dirty.
Mount JFS Failure: -22
jfs_mount failed w/return code = -22

What shall I do now?

Thanks for your Feedback.

Zeno

On Mon, 08 Mar 2004 19:59:56 -0800
"Sumit Narayan" <reachsumit@...> wrote:

> I guess you can download the latest kernel, enable JFS in it, and
then 
> mount. It should mount easily then.
> 
> --Sumit
> 
> ----------------------------------------------------------------------
--------
> Math Problem? Call : 1- 800 - (sin^2*e/ln x) - log(x+y/e^5)
> 
> 
> >From: "Zeno R.R. Davatz" <zdavatz@...>
> >To: "jfs-discussion@..." 
> ><jfs-discussion@...>
> >Subject: Re: [Jfs-discussion] jfs does not mount
> >Date: Mon, 8 Mar 2004 14:35:50 +0100
> >
> >On Mon, 08 Mar 2004 14:24:59 +0100
> >"Per Jessen" <per@...> wrote:
> >
> > > On Mon, 8 Mar 2004 08:57:15 +0100, Zeno R.R. Davatz wrote:
> > >
> > > >mount /dev/hda3 /mnt/gentoo
> > > >
> > > >But then mount tells me it could not mount the jfs on
/mnt/gentoo.
> > > >It say bad superblock, wrong fs or to many mounted file systems.
> > > >Any hints why I can not mount jfs when I boot from a Gentoo CD?
> > >
> > > 1) Either specify '-t jfs' when you mount or
> > > 2) add 'jfs' to /etc/filesystems
> >Ok, thanks. I believe JFS is not on the Gentoo CD in Kernel (And
somehow 
> >the newest Gentoo CD's won't boot).
> >
> >Thanks
> >Zeno
> >_______________________________________________
> >Jfs-discussion mailing list
> >Jfs-discussion@...
> >http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-
discussion
> 
> _________________________________________________________________
> Find things fast with the new MSN Toolbar ? includes FREE pop-up
blocking! 
> http://clk.atdmt.com/AVE/go/onm00200414ave/direct/01/
> 
> 


-- 
Mit freundlichen Gr?sen / best regards

Zeno Davatz
Verkauf & Akquisition

+41 1 350 85 86

 http://www.ywesee.com > intellectual capital connected > http://www.oddb.org

--__--__--

Message: 2
Date: Tue, 9 Mar 2004 10:11:20 +0100
From: "Zeno R.R. Davatz" <zdavatz@...>
To: jfs-discussion@...
Subject: Re: [Jfs-discussion] jfs does not mount
Organization: ywesee - intellectual capital connected

On Tue, 9 Mar 2004 10:07:32 +0100
"Zeno R.R. Davatz" <zdavatz@...> wrote:

> Hi 
> 
> Thanks for all the kind replys.
> 
> I downloaded the latest gentoo-Universal CD. 
> 
> When I do mount /dev/hda3 /mnt/gentoo I get:
> jfs_mount: Mount Failure: File System Dirty.
> Mount JFS Failure: -22
> jfs_mount failed w/return code = -22
ok, fsck.jfs done the rest.

Thanks again.

Zeno
PS: Great weather today in Zurich. ;-)

> 
> What shall I do now?
> 
> Thanks for your Feedback.
> 
> Zeno
> 
> On Mon, 08 Mar 2004 19:59:56 -0800
> "Sumit Narayan" <reachsumit@...> wrote:
> 
> > I guess you can download the latest kernel, enable JFS in it, and
then 
> > mount. It should mount easily then.
> > 
> > --Sumit
> > 
> > --------------------------------------------------------------------
----------
> > Math Problem? Call : 1- 800 - (sin^2*e/ln x) - log(x+y/e^5)
> > 
> > 
> > >From: "Zeno R.R. Davatz" <zdavatz@...>
> > >To: "jfs-discussion@..." 
> > ><jfs-discussion@...>
> > >Subject: Re: [Jfs-discussion] jfs does not mount
> > >Date: Mon, 8 Mar 2004 14:35:50 +0100
> > >
> > >On Mon, 08 Mar 2004 14:24:59 +0100
> > >"Per Jessen" <per@...> wrote:
> > >
> > > > On Mon, 8 Mar 2004 08:57:15 +0100, Zeno R.R. Davatz wrote:
> > > >
> > > > >mount /dev/hda3 /mnt/gentoo
> > > > >
> > > > >But then mount tells me it could not mount the jfs on
/mnt/gentoo.
> > > > >It say bad superblock, wrong fs or to many mounted file
systems.
> > > > >Any hints why I can not mount jfs when I boot from a Gentoo CD?
> > > >
> > > > 1) Either specify '-t jfs' when you mount or
> > > > 2) add 'jfs' to /etc/filesystems
> > >Ok, thanks. I believe JFS is not on the Gentoo CD in Kernel (And
somehow 
> > >the newest Gentoo CD's won't boot).
> > >
> > >Thanks
> > >Zeno
> > >_______________________________________________
> > >Jfs-discussion mailing list
> > >Jfs-discussion@...
> > >http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-
discussion
> > 
> > _________________________________________________________________
> > Find things fast with the new MSN Toolbar _ includes FREE pop-up
blocking! 
> > http://clk.atdmt.com/AVE/go/onm00200414ave/direct/01/
> > 
> > 
> 
> 
> -- 
> Mit freundlichen Gr?sen / best regards
> 
> Zeno Davatz
> Verkauf & Akquisition
> 
> +41 1 350 85 86
> 
> http://www.ywesee.com > intellectual capital connected > http://www.oddb.org
> _______________________________________________
> Jfs-discussion mailing list
> Jfs-discussion@...
> http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-
discussion
> 


-- 
Mit freundlichen Gr?sen / best regards

Zeno Davatz
Verkauf & Akquisition

+41 1 350 85 86

 http://www.ywesee.com > intellectual capital connected > http://www.oddb.org

--__--__--

Message: 3
Date: Tue, 9 Mar 2004 11:15:17 +0100
From: "Zeno R.R. Davatz" <zdavatz@...>
To: "jfs-discussion@..."
 <jfs-discussion@...>
Organization: ywesee - intellectual capital connected
Subject: [Jfs-discussion] Phase 7 Errors detected in Fileset
File/Directory Allocation Map
 control information

Hi

My HDD with jfs does not want to get mounted.

I do fsck.jfs -f and I get:
Phase 1-6 ok
Phase 7: Errors detected in the Fileset File/Directory Allocation Map
control information
Phase 8: Incorrect data detected in disk allocation structures and
control structures
File System  checked READ ONLY.
File System is dirty.
File System ist dirty but is marked clean. In its present state, the
results of acccessing /dev/hda3 (except by this utility) are undefined.

Any hints?

Thanks for your Feedback.
Zeno

-- 
Mit freundlichen Gr?sen / best regards

Zeno Davatz
Verkauf & Akquisition

+41 1 350 85 86

 http://www.ywesee.com > intellectual capital connected > http://www.oddb.org

--__--__--

Message: 4
From: "Per Jessen" <per@...>
To: "jfs-discussion@..." <jfs-discussion@...
126.southbury.usf.ibm.com>
Date: Tue, 09 Mar 2004 12:49:44 +0100
Subject: Re: [Jfs-discussion] Phase 7 Errors detected in Fileset
File/Directory Allocation Map control information

On Tue, 9 Mar 2004 11:15:17 +0100, Zeno R.R. Davatz wrote:

>
>Any hints?
>

To start with, make sure you have the latest version of jfsutils -
1.1.5 I believe it is. 
Second, I did have a situation that looked similar to what you've
reported, but
I no longer have the log available, so I can't say it really was the
same. 

However, I ended up fscking the filesystem without replaying the log,
which did the trick.  
I'm fairly certain this was caused by a hardware problem, probably
related to the log. 
See 'man fsck.jfs' for how to fsck without replaying the log - and note
the warnings!


/Per Jessen, Zurich
and it is indeed a beautiful spring weather in Zurich today!



--__--__--

Message: 5
Subject: Re: [Jfs-discussion] Phase 7 Errors detected in Fileset
	File/Directory Allocation Map control information
From: Dave Kleikamp <shaggy@...>
To: "Zeno R.R. Davatz" <zdavatz@...>
Cc: JFS Discussion <jfs-discussion@...>
Date: Tue, 09 Mar 2004 07:40:08 -0600

On Tue, 2004-03-09 at 04:15, Zeno R.R. Davatz wrote:
> Hi
> 
> My HDD with jfs does not want to get mounted.
> 
> I do fsck.jfs -f and I get:
> Phase 1-6 ok
> Phase 7: Errors detected in the Fileset File/Directory Allocation Map
control information
> Phase 8: Incorrect data detected in disk allocation structures and
control structures
> File System  checked READ ONLY.

I'm not sure why fsck.jfs is checking the file system READ ONLY. 
Normally it runs in read-write mode unless the -n flag is specified. 
Other reasons for checking READ ONLY are if the file system is mounted
or if you do not have write access to the device.

Did fsck.jfs print any messages indicating why it was running read-only
before the phase 1 message?

> File System is dirty.
> File System is dirty but is marked clean. In its present state, the
results of accessing /dev/hda3 (except by this utility) are undefined.

This is odd.  fsck.jfs is reporting that the file system is marked clean
(even though it decided it should be dirty), but the mount failure
indicates that it is not marked clean.

> Any hints?

I'm a bit confused.

> 
> Thanks for your Feedback.
> Zeno

Thanks,
Shaggy
-- 
David Kleikamp
IBM Linux Technology Center


--__--__--

Message: 6
Date: Tue, 9 Mar 2004 15:22:35 +0100
From: "Zeno R.R. Davatz" <zdavatz@...>
To: jfs-discussion@...
Subject: Re: [Jfs-discussion] Phase 7 Errors detected in Fileset
 File/Directory Allocation Map control information
Organization: ywesee - intellectual capital connected

Ok, thanks for the replies.

I installed jfsutils 1.1.5 and now jfs on /dev/hda3 works great.

Now ext2 gives me problems on /dev/hda1.

Is it possible to put a jfs for a boot partition? Then I will exchange
the ext2 with jfs.

Thanks
Zeno

On Tue, 09 Mar 2004 12:49:44 +0100
"Per Jessen" <per@...> wrote:

> On Tue, 9 Mar 2004 11:15:17 +0100, Zeno R.R. Davatz wrote:
> 
> >
> >Any hints?
> >
> 
> To start with, make sure you have the latest version of jfsutils -
1.1.5 I believe it is. 
> Second, I did have a situation that looked similar to what you've
reported, but
> I no longer have the log available, so I can't say it really was the
same. 
> 
> However, I ended up fscking the filesystem without replaying the log,
which did the trick.  
> I'm fairly certain this was caused by a hardware problem, probably
related to the log. 
> See 'man fsck.jfs' for how to fsck without replaying the log - and
note the warnings!
> 
> 
> /Per Jessen, Zurich
> and it is indeed a beautiful spring weather in Zurich today!
> 
> 
> _______________________________________________
> Jfs-discussion mailing list
> Jfs-discussion@...
> http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-
discussion
> 


-- 
Mit freundlichen Gr?sen / best regards

Zeno Davatz
Verkauf & Akquisition

+41 1 350 85 86

 http://www.ywesee.com > intellectual capital connected > http://www.oddb.org


--__--__--

_______________________________________________
Jfs-discussion mailing list
Jfs-discussion@...
http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-
discussion


End of Jfs-discussion Digest

Hi

My HDD with jfs does not want to get mounted.

I do fsck.jfs -f and I get:
Phase 1-6 ok
Phase 7: Errors detected in the Fileset File/Directory Allocation Map control information
Phase 8: Incorrect data detected in disk allocation structures and control structures
File System  checked READ ONLY.
File System is dirty.
File System ist dirty but is marked clean. In its present state, the results of acccessing /dev/hda3 (except by this utility) are undefined.

Any hints?

Thanks for your Feedback.
Zeno

-- 
Mit freundlichen Grüssen / best regards

Zeno Davatz
Verkauf & Akquisition

+41 1 350 85 86

 http://www.ywesee.com > intellectual capital connected > http://www.oddb.org