Dear list,
we have the OSTs on shared storage, but configured with a journal
device on local disks of the OSS. Is it possible to re-mount an OST
with a new journal device? A simple mount -t lustre after removing
and reconfiguring a journal with the same name did not work.
Regards, Ralf
--
Ralf Utermann
_____________________________________________________________________
Universit?t Augsburg, Institut f?r Physik -- EDV-Betreuer
Universit?tsstr.1
D-86135 Augsburg Phone: +49-821-598-3231
SMTP: Ralf.Utermann at Physik.Uni-Augsburg.DE Fax: -3411
Assuming you already did the ''mke2fs -O journal_dev external-journal'' step, have you followed with a ''tune2fs -J device=<new journaldev>'' command to tell the fs that the location of the external journal has changed? On Dec 3, 2008, at 12:11 AM, Ralf Utermann wrote:> Dear list, > > we have the OSTs on shared storage, but configured with a journal > device on local disks of the OSS. Is it possible to re-mount an OST > with a new journal device? A simple mount -t lustre after removing > and reconfiguring a journal with the same name did not work. > > Regards, Ralf > -- > Ralf Utermann > _____________________________________________________________________ > Universit?t Augsburg, Institut f?r Physik -- EDV-Betreuer > Universit?tsstr.1 > D-86135 Augsburg Phone: +49-821-598-3231 > SMTP: Ralf.Utermann at Physik.Uni-Augsburg.DE Fax: -3411 > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss-------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2421 bytes Desc: not available Url : http://lists.lustre.org/pipermail/lustre-discuss/attachments/20081203/bc3352bc/attachment.bin
On Dec 03, 2008 09:11 +0100, Ralf Utermann wrote:> we have the OSTs on shared storage, but configured with a journal > device on local disks of the OSS. Is it possible to re-mount an OST > with a new journal device?No, this would require a full filesystem check and would be no better than running without a journal. Even worse, if you go back to the original node + journal and it is still marked dirty then it may "recover" by overwriting the filesystem with old metadata. The journal needs to be created on shared storage along with the filesystem.> A simple mount -t lustre after removing > and reconfiguring a journal with the same name did not work.If this is a one-time event (i.e. you want to reconfigure your filesystem to use a journal on a shared device) then you can do this by removing the journal (preferrably on the original node after a clean unmount) with: tune2fs -O ^has_journal {filesystem_dev} e2fsck -f {filesystem_dev} (not sure if required) tune2fs -J device={journal_dev} {filesystem_dev} Cheers, Andreas -- Andreas Dilger Sr. Staff Engineer, Lustre Group Sun Microsystems of Canada, Inc.
Andreas Dilger wrote: [...]> > tune2fs -O ^has_journal {filesystem_dev} > e2fsck -f {filesystem_dev} (not sure if required) > tune2fs -J device={journal_dev} {filesystem_dev}we are just starting with Lustre, so this has been more or less a test environment. Will set up the journal on shared storage for production. For this case: I could not remove the has_journal entry, probably because I removed the old journal device before doing this: alcc-ost1:~# tune2fs -f -O ^has_journal /dev/vgoss1/ost1 tune2fs 1.40.11.sun1 (17-June-2008) The needs_recovery flag is set. Please run e2fsck before clearing the has_journal flag. alcc-ost1:~# e2fsck /dev/vgoss1/ost1 e2fsck 1.40.11.sun1 (17-June-2008) External journal does not support this filesystem Thanks for your help, Frank and Andreas, Bye, Ralf -- Ralf Utermann _____________________________________________________________________ Universit?t Augsburg, Institut f?r Physik -- EDV-Betreuer Universit?tsstr.1 D-86135 Augsburg Phone: +49-821-598-3231 SMTP: Ralf.Utermann at Physik.Uni-Augsburg.DE Fax: -3411