Thanks Brian, but, I have tested it already with at least one partition:
e2fsck -fy /dev/sdb1 but anyhow the client still do not see it after a partition remount. It could be possible that I need to switch the entire server off and restart it? What else I could check ? Cheers, Giacinto -- -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Giacinto Donvito LIBI -- EGEE3 SA1 INFN - Bari ITALY ------------------------------------------------------------------ [email protected] | GTalk/GMail: [email protected] tel. +39 080 5443244 Fax +39 0805442470 | Skype: giacinto_it VOIP: +41225481596 | MSN: [email protected] AIM/iChat: gdonvito1 | Yahoo: eric1_it ------------------------------------------------------------------ "A lie gets halfway around the world before the truth has a chance to get its pants on." - Sir Winston Churchill (1874-1965) Il giorno 26/gen/2010, alle ore 18.46, Brian J. Murrell ha scritto: > On Tue, 2010-01-26 at 15:48 +0100, Giacinto Donvito wrote: >> >> Jan 26 14:43:59 dot1-se-01 kernel: LustreError: >> 6542:0:(filter_io_26.c:684:filter_commitrw_write()) error starting >> transaction: rc = -30 > > Your target is read-only, typically because ldiskfs has found a critical > error and switched the target to read-only to prevent any further > damage. > > You need to e2fsck -f that (and perhaps more) target(s). > > b. > > > _______________________________________________ > Lustre-discuss mailing list > [email protected] > http://lists.lustre.org/mailman/listinfo/lustre-discuss
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
