Good morning,
jfsutils-1.1.4-1
I've problem with my hard drive with JFS filesystem. I using Fedora Core 2 with 
default kernel 2.6.5-1.358 and jfsutils-1.1.4-1.
While my work I've got error message:

Aug 29 18:41:26 vox kernel: ERROR: (device hdg1): diRead: i_ino != di_number
Aug 29 18:41:26 vox kernel: hdg: 0 bytes in FIFO
Aug 29 18:41:26 vox kernel: hdg: timeout waiting for DMA
Aug 29 18:41:26 vox kernel: ERROR: (device hdg1): diRead: i_ino != di_number
Aug 29 18:41:27 vox last message repeated 14 times
Aug 29 18:41:27 vox kernel: hdg: 0 bytes in FIFO
Aug 29 18:41:27 vox kernel: hdg: timeout waiting for DMA
Aug 29 18:41:27 vox kernel: hdg: 0 bytes in FIFO
Aug 29 18:41:27 vox kernel: hdg: timeout waiting for DMA
Aug 29 18:41:27 vox kernel: ERROR: (device hdg1): DT_GETPAGE: dtree page corrupt
Aug 29 18:41:27 vox last message repeated 2 times
Aug 29 18:41:27 vox kernel: hdg: 0 bytes in FIFO
Aug 29 18:41:27 vox kernel: hdg: timeout waiting for DMA
Aug 29 18:41:27 vox kernel: ERROR: (device hdg1): DT_GETPAGE: dtree page corrupt
Aug 29 18:41:27 vox kernel: hdg: 0 bytes in FIFO
Aug 29 18:41:27 vox kernel: hdg: timeout waiting for DMA
Aug 29 18:41:27 vox kernel: ERROR: (device hdg1): DT_GETPAGE: dtree page corrupt
Aug 29 18:41:27 vox kernel: hdg: 0 bytes in FIFO
Aug 29 18:41:27 vox kernel: hdg: timeout waiting for DMA
Aug 29 18:41:27 vox kernel: ERROR: (device hdg1): DT_GETPAGE: dtree page corrupt
Aug 29 18:41:27 vox kernel: hdg: 0 bytes in FIFO
Aug 29 18:41:27 vox kernel: hdg: timeout waiting for DMA
Aug 29 18:41:27 vox kernel: ERROR: (device hdg1): DT_GETPAGE: dtree page corrupt
Aug 29 18:41:27 vox kernel: hdg: 0 bytes in FIFO
Aug 29 18:41:27 vox kernel: hdg: timeout waiting for DMA
Aug 29 18:41:27 vox kernel: ERROR: (device hdg1): DT_GETPAGE: dtree page corrupt
Aug 29 18:41:27 vox kernel: hdg: 0 bytes in FIFO
Aug 29 18:41:27 vox kernel: hdg: timeout waiting for DMA
Aug 29 18:41:28 vox kernel: hdg: 0 bytes in FIFO
Aug 29 18:41:28 vox kernel: hdg: timeout waiting for DMA
Aug 29 18:41:28 vox kernel: hdg: 0 bytes in FIFO
Aug 29 18:41:28 vox kernel: hdg: timeout waiting for DMA
Aug 29 18:41:33 vox kernel: hdg: dma_intr: status=0xff { Busy }
Aug 29 18:41:33 vox kernel: 
Aug 29 18:41:33 vox kernel: hdg: DMA disabled
Aug 29 18:41:33 vox kernel: hdh: DMA disabled
Aug 29 18:41:33 vox kernel: ide3: reset: master: error (0x00?)

I don't care about it, but next day i want mount JFS drive...
this is my way

[EMAIL PROTECTED] root]# mount -t jfs /dev/hdg1 /mnt/120gb/
mount: wrong fs type, bad option, bad superblock on /dev/hdb1,
       or too many mounted file systems

[EMAIL PROTECTED] root]# jfs_fsck /dev/hdg1
jfs_fsck version 1.1.4, 30-Oct-2003
processing started: 9/2/2004 23.47.10
Using default parameter: -p
The current device is:  /dev/hdg1
Block size in bytes:  4096
Filesystem size in blocks:  29304560
**Phase 0 - Replay Journal Log
**Phase 1 - Check Blocks, Files/Directories, and  Directory Entries
Filesystem is clean.

[EMAIL PROTECTED] root]# mount -t jfs /dev/hdg1 /mnt/120gb/

[EMAIL PROTECTED] root]# ls /mnt/120gb/
ls: reading directory /mnt/120gb/: Input/output error

So, I don't know what this mean. I thing that isn't hard drive problem, because after 
that i do
[EMAIL PROTECTED] root]# dd if=/dev/hdg1 /dev/hdb1
without any error, and utils from manufacturer (SeaGate) says, there is no hardware 
problem. And the problem is the same. I can mount partition after fsck, but i can't 
list. 
So I ask: I lost all of my date, without hope fo safe?
Realy there is no way how I get data back? Why happen this?

My hw:
Athlon 1600+, SIS745, 768MB RAM,
hda: system (boot,swap,root) ext3
hdb: 160GB (Seagate) jfs
hdc: DVD
hdd: DVD

Abit Hot Rod 100 - HPT 370 chipset
hde: 80GB (WD) jfs
hdg: 120GB (Seagate) jfs !!!!!
hdh: 60GB (Seagate) jfs

thank you for all advices.
sorry for my pure English
I'm not sure if I write all relevant information.
Petr Humlicek
[EMAIL PROTECTED]





_______________________________________________
Jfs-discussion mailing list
[EMAIL PROTECTED]
http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion

Reply via email to