On 6/28/05 2:47 PM, "Dave Kleikamp" <[EMAIL PROTECTED]> wrote:
> On Tue, 2005-06-28 at 13:56 -0700, Jeff Block wrote:
>> Forgive me if this issue has already been seen on this list, I was unable to
>> find...
>>
>> I had setup two jfs filesystems to journal to two separate external journal
>> devices. The two jfs filesystems are /dev/sda1 and /dev/sdb1. The external
>> journal devices are /dev/md7 and /dev/md8. The md devices were created
>> using mdadm to setup mirrors on two internal scsi disks. The jfs
>> filesystems, /dev/sda1 and /dev/sdb1 are on an external RAID box.
>>
>> The problem that I'm having is, after a reboot, neither of the filesystems
>> would mount read/write. I could mount read-only.
>
> Running jfs_fsck against /dev/sda1 & /dev/sdb1 is all that needs to be
> done. If these file systems are listed correctly in /etc/fstab, with
> the last field non-zero, it should happen automatically at boot.
Fsck was being run at boot. And, when booted into single user mode, the
mount did seem to work without re-attaching the journal. Unfortunately, I
can't debug this any further until I get it back to where it was.
>
>> So, we figured journal
>> problem and reattached the external journal devices using 'jfs_tune -J
>> device=/dev/md7 /dev/sda1'. But, again, after a reboot, the journal devices
>> could not be found and so we had to re-attach again.
>
> Did fsck get run against the drives? On boot, fsck should locate the
> external journals, even if the device numbers changed after a reboot.
> If you are running fsck against sda1 & sdb1, are they reporting any
> errors?
No, fsck was reporting clean devices.
>
>> We did this several times and tried to determine what was changing and
>> causing the journal to not be found. At some point in this process, both of
>> the external journal devices became corrupt and now I can't mount read/write
>> at all.
>>
>> I've tried to re-initialize the devices with:
>> mkfs_jfs -J journal_dev /dev/md7, but this fails with "The specified disk
>> did not finish formatting".
>> When I try and attach the external journal to a filesystem, I get "Error
>> attaching JFS external journal to JFS FS".
>>
>> I can mkfs_jfs /dev/md7 just fine. But, when I try and format it as a
>> journal device, it fails. An strace on the process shows:
>> ...open("/dev/md7", ) ..... (Device or resource busy)...
>
> Hmm. If the mount fails, jfs should be releasing the journal device so
> that it wouldn't be busy. There might be a problem in the error path,
> even though from a quick look at the code, it seems right.
>
> In fact this is very strange because in both cases, mkfs_jfs should be
> opening the device with O_RDWR | O_EXCL. I'm not sure why one would
> fail and the other succeed.
Here's the exact line from the strace:
open("/dev/sdc8", O_RDWR|O_EXCL|O_LARGEFILE) = -1 EBUSY (Device or resource
busy)
write(1, "The specified disk did not finis"..., 46The specified disk did not
finish formatting.
Thanks for the help.
Jeff
>
>> I'm running Redhat Enterprise Linux 4 with a 2.6.9-5.0.5 kernel. This is
>> the default redhat kernel with some extra filesystem support added
>> (including jfs external journaling).
>>
>> Thanks in advance for any help offered.
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Jfs-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jfs-discussion
