Hello, I have a corrupt file than I can???t delete. This is my file:>ls ???la .viminfo-????????? ? ? ? ? ? .viminfo>lfs getstripe .viminfo.viminfo lmm_stripe_count: 6 lmm_stripe_size: 1048576 lmm_layout_gen: 0 lmm_stripe_offset: 18 obdidx objid objid group 18 1442898 0x160452 0 22 48 0x30 0 19 1442770 0x1603d2 0 21 49 0x31 0 23 48 0x30 0 20 50 0x32 0 And these are my OST:>lctl dl0 UP mgc MGC192.168.11.9 at tcp f6d5b76f-a7e0-61ca-b389-cb3896b86186 5 1 UP lov cetafs-clilov-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 4 2 UP lmv cetafs-clilmv-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 4 3 UP mdc cetafs-MDT0000-mdc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 4 UP osc cetafs-OST0000-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 5 UP osc cetafs-OST0001-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 6 UP osc cetafs-OST0002-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 7 UP osc cetafs-OST0003-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 8 UP osc cetafs-OST0004-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 9 UP osc cetafs-OST0005-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 10 UP osc cetafs-OST0006-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 11 UP osc cetafs-OST0007-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 12 UP osc cetafs-OST0012-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 13 UP osc cetafs-OST0013-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 14 UP osc cetafs-OST0008-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 15 UP osc cetafs-OST000a-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 16 UP osc cetafs-OST0009-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 17 UP osc cetafs-OST000b-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 18 UP osc cetafs-OST000c-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 19 UP osc cetafs-OST000d-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 20 UP osc cetafs-OST000e-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 21 UP osc cetafs-OST000f-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 22 UP osc cetafs-OST0010-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 23 UP osc cetafs-OST0011-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 24 UP osc cetafs-OST0018-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 25 UP osc cetafs-OST0015-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 26 UP osc cetafs-OST0016-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 27 UP osc cetafs-OST0017-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 When I try to delete the file I got the next menssage:> rm .viminform: cannot remove `.viminfo'': Invalid argument How can I do to delete the file? THANKS! Alfonso Pardo D??az Researcher / System Administrator at CETA-Ciemat c/ Sola n?? 1; 10200 Trujillo, ESPA??A Tel: +34 927 65 93 17 Fax: +34 927 32 32 37 ---------------------------- Confidencialidad: Este mensaje y sus ficheros adjuntos se dirige exclusivamente a su destinatario y puede contener informaci?n privilegiada o confidencial. Si no es vd. el destinatario indicado, queda notificado de que la utilizaci?n, divulgaci?n y/o copia sin autorizaci?n est? prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente respondiendo al mensaje y proceda a su destrucci?n. Disclaimer: This message and its attached files is intended exclusively for its recipients and may contain confidential information. If you received this e-mail in error you are hereby notified that any dissemination, copy or disclosure of this communication is strictly prohibited and may be unlawful. In this case, please notify us by a reply and delete this email and its contents immediately. ---------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.lustre.org/pipermail/lustre-discuss/attachments/20130307/a7180cff/attachment.html
The snarky reply would be to use Emacs. More seriously: When I see something like ?????? in the attributes for a file, my first thought is that the group_upcall on the filesystem is not correct, so permissions are broken. If you can log on as root, you may be able to see it clearly. If that doesn''t work, you may have to run an fsck on the MDT (which may take minutes to hours depending on the size of your MDT) If that doesn''t work, follow the procedure for running an lfsck (which will take a long time, and require quite a bit of storage to execute) -Ben Evans ________________________________ From: lustre-discuss-bounces at lists.lustre.org [lustre-discuss-bounces at lists.lustre.org] on behalf of Alfonso Pardo [alfonso.pardo at ciemat.es] Sent: Thursday, March 07, 2013 10:09 AM To: lustre-discuss at lists.lustre.org; wc-discuss at whamcloud.com Subject: [Lustre-discuss] delete a "undeletable" file Hello, I have a corrupt file than I can?t delete. This is my file:>ls ?la .viminfo-????????? ? ? ? ? ? .viminfo>lfs getstripe .viminfo.viminfo lmm_stripe_count: 6 lmm_stripe_size: 1048576 lmm_layout_gen: 0 lmm_stripe_offset: 18 obdidx objid objid group 18 1442898 0x160452 0 22 48 0x30 0 19 1442770 0x1603d2 0 21 49 0x31 0 23 48 0x30 0 20 50 0x32 0 And these are my OST:>lctl dl0 UP mgc MGC192.168.11.9 at tcp f6d5b76f-a7e0-61ca-b389-cb3896b86186 5 1 UP lov cetafs-clilov-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 4 2 UP lmv cetafs-clilmv-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 4 3 UP mdc cetafs-MDT0000-mdc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 4 UP osc cetafs-OST0000-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 5 UP osc cetafs-OST0001-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 6 UP osc cetafs-OST0002-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 7 UP osc cetafs-OST0003-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 8 UP osc cetafs-OST0004-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 9 UP osc cetafs-OST0005-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 10 UP osc cetafs-OST0006-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 11 UP osc cetafs-OST0007-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 12 UP osc cetafs-OST0012-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 13 UP osc cetafs-OST0013-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 14 UP osc cetafs-OST0008-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 15 UP osc cetafs-OST000a-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 16 UP osc cetafs-OST0009-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 17 UP osc cetafs-OST000b-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 18 UP osc cetafs-OST000c-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 19 UP osc cetafs-OST000d-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 20 UP osc cetafs-OST000e-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 21 UP osc cetafs-OST000f-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 22 UP osc cetafs-OST0010-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 23 UP osc cetafs-OST0011-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 24 UP osc cetafs-OST0018-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 25 UP osc cetafs-OST0015-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 26 UP osc cetafs-OST0016-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 27 UP osc cetafs-OST0017-osc-ffff88009816e400 a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5 When I try to delete the file I got the next menssage:> rm .viminform: cannot remove `.viminfo'': Invalid argument How can I do to delete the file? THANKS! Alfonso Pardo D?az Researcher / System Administrator at CETA-Ciemat c/ Sola n? 1; 10200 Trujillo, ESPA?A Tel: +34 927 65 93 17 Fax: +34 927 32 32 37 [CETA-Ciemat logo]<http://www.ceta-ciemat.es/> ---------------------------- Confidencialidad: Este mensaje y sus ficheros adjuntos se dirige exclusivamente a su destinatario y puede contener informaci?n privilegiada o confidencial. Si no es vd. el destinatario indicado, queda notificado de que la utilizaci?n, divulgaci?n y/o copia sin autorizaci?n est? prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente respondiendo al mensaje y proceda a su destrucci?n. Disclaimer: This message and its attached files is intended exclusively for its recipients and may contain confidential information. If you received this e-mail in error you are hereby notified that any dissemination, copy or disclosure of this communication is strictly prohibited and may be unlawful. In this case, please notify us by a reply and delete this email and its contents immediately. ---------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.lustre.org/pipermail/lustre-discuss/attachments/20130307/78dae331/attachment.html
Hi, If the file is disassociated with an OST which is offline, bring the OST back online, if the OST object it self is missing then you can remove the file using ''unlink'' rather than ''rm'' to unlink the object meta data. If you want to try and recover the missing OST object an lfs getstripe against the file should yield the the OST on which it resides. Once that''s determined you can take that OST offline and e2fsck may successfully restore it. Another option as Ben correctly points out, lfsck will correct / prune this meta data as well as the now orphaned (if any) OST object. -cf On 03/07/2013 08:30 AM, Ben Evans wrote:> The snarky reply would be to use Emacs. > > More seriously: > > When I see something like ?????? in the attributes for a file, my > first thought is that the group_upcall on the filesystem is not > correct, so permissions are broken. If you can log on as root, you may > be able to see it clearly. > > If that doesn''t work, you may have to run an fsck on the MDT (which > may take minutes to hours depending on the size of your MDT) > > If that doesn''t work, follow the procedure for running an lfsck (which > will take a long time, and require quite a bit of storage to execute) > > -Ben Evans > > ------------------------------------------------------------------------ > *From:* lustre-discuss-bounces at lists.lustre.org > [lustre-discuss-bounces at lists.lustre.org] on behalf of Alfonso Pardo > [alfonso.pardo at ciemat.es] > *Sent:* Thursday, March 07, 2013 10:09 AM > *To:* lustre-discuss at lists.lustre.org; wc-discuss at whamcloud.com > *Subject:* [Lustre-discuss] delete a "undeletable" file > > Hello, > I have a corrupt file than I can?t delete. > This is my file: > >ls ?la .viminfo > /-????????? ? ? ? ? ? .viminfo/ > />lfs getstripe .viminfo/ > /.viminfo/ > /lmm_stripe_count: 6/ > /lmm_stripe_size: 1048576/ > /lmm_layout_gen: 0/ > /lmm_stripe_offset: 18/ > /obdidx objid objid group/ > /18 1442898 0x160452 0/ > /22 48 0x30 0/ > /19 1442770 0x1603d2 0/ > /21 49 0x31 0/ > /23 48 0x30 0/ > /20 50 0x32 0/ > And these are my OST: > />lctl dl/ > /0 UP mgc MGC192.168.11.9 at tcp f6d5b76f-a7e0-61ca-b389-cb3896b86186 5/ > /1 UP lov cetafs-clilov-ffff88009816e400 > a7ba6783-6ed8-2197-4ffc-fecbff9860a5 4/ > /2 UP lmv cetafs-clilmv-ffff88009816e400 > a7ba6783-6ed8-2197-4ffc-fecbff9860a5 4/ > /3 UP mdc cetafs-MDT0000-mdc-ffff88009816e400 > a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > /4 UP osc cetafs-OST0000-osc-ffff88009816e400 > a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > /5 UP osc cetafs-OST0001-osc-ffff88009816e400 > a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > /6 UP osc cetafs-OST0002-osc-ffff88009816e400 > a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > /7 UP osc cetafs-OST0003-osc-ffff88009816e400 > a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > /8 UP osc cetafs-OST0004-osc-ffff88009816e400 > a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > /9 UP osc cetafs-OST0005-osc-ffff88009816e400 > a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > /10 UP osc cetafs-OST0006-osc-ffff88009816e400 > a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > /11 UP osc cetafs-OST0007-osc-ffff88009816e400 > a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > /12 UP osc cetafs-OST0012-osc-ffff88009816e400 > a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > /13 UP osc cetafs-OST0013-osc-ffff88009816e400 > a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > /14 UP osc cetafs-OST0008-osc-ffff88009816e400 > a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > /15 UP osc cetafs-OST000a-osc-ffff88009816e400 > a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > /16 UP osc cetafs-OST0009-osc-ffff88009816e400 > a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > /17 UP osc cetafs-OST000b-osc-ffff88009816e400 > a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > /18 UP osc cetafs-OST000c-osc-ffff88009816e400 > a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > /19 UP osc cetafs-OST000d-osc-ffff88009816e400 > a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > /20 UP osc cetafs-OST000e-osc-ffff88009816e400 > a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > /21 UP osc cetafs-OST000f-osc-ffff88009816e400 > a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > /22 UP osc cetafs-OST0010-osc-ffff88009816e400 > a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > /23 UP osc cetafs-OST0011-osc-ffff88009816e400 > a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > /24 UP osc cetafs-OST0018-osc-ffff88009816e400 > a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > /25 UP osc cetafs-OST0015-osc-ffff88009816e400 > a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > /26 UP osc cetafs-OST0016-osc-ffff88009816e400 > a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > /27 UP osc cetafs-OST0017-osc-ffff88009816e400 > a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > When I try to delete the file I got the next menssage: > /> rm .viminfo/ > /rm: cannot remove `.viminfo'': Invalid argument/ > How can I do to delete the file? > THANKS! > > // > > // > > // > > // > > /Alfonso Pardo D?az > /*/Researcher / System Administrator at CETA-Ciemat /* > /c/ Sola n? 1; 10200 Trujillo, ESPA?A/ > /Tel: +34 927 65 93 17 Fax: +34 927 32 32 37/ > > CETA-Ciemat logo <http://www.ceta-ciemat.es/> > > ---------------------------- Confidencialidad: Este mensaje y sus > ficheros adjuntos se dirige exclusivamente a su destinatario y puede > contener informaci?n privilegiada o confidencial. Si no es vd. el > destinatario indicado, queda notificado de que la utilizaci?n, > divulgaci?n y/o copia sin autorizaci?n est? prohibida en virtud de la > legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos > que nos lo comunique inmediatamente respondiendo al mensaje y proceda > a su destrucci?n. Disclaimer: This message and its attached files is > intended exclusively for its recipients and may contain confidential > information. If you received this e-mail in error you are hereby > notified that any dissemination, copy or disclosure of this > communication is strictly prohibited and may be unlawful. In this > case, please notify us by a reply and delete this email and its > contents immediately. ---------------------------- > > > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss
You could just unlink it instead. That will work when rm fails. bob On 3/7/2013 11:10 AM, Colin Faber wrote:> Hi, > > If the file is disassociated with an OST which is offline, bring the OST > back online, if the OST object it self is missing then you can remove > the file using ''unlink'' rather than ''rm'' to unlink the object meta data. > > If you want to try and recover the missing OST object an lfs getstripe > against the file should yield the the OST on which it resides. Once > that''s determined you can take that OST offline and e2fsck may > successfully restore it. > > Another option as Ben correctly points out, lfsck will correct / prune > this meta data as well as the now orphaned (if any) OST object. > > -cf > > > On 03/07/2013 08:30 AM, Ben Evans wrote: >> The snarky reply would be to use Emacs. >> >> More seriously: >> >> When I see something like ?????? in the attributes for a file, my >> first thought is that the group_upcall on the filesystem is not >> correct, so permissions are broken. If you can log on as root, you may >> be able to see it clearly. >> >> If that doesn''t work, you may have to run an fsck on the MDT (which >> may take minutes to hours depending on the size of your MDT) >> >> If that doesn''t work, follow the procedure for running an lfsck (which >> will take a long time, and require quite a bit of storage to execute) >> >> -Ben Evans >> >> ------------------------------------------------------------------------ >> *From:* lustre-discuss-bounces at lists.lustre.org >> [lustre-discuss-bounces at lists.lustre.org] on behalf of Alfonso Pardo >> [alfonso.pardo at ciemat.es] >> *Sent:* Thursday, March 07, 2013 10:09 AM >> *To:* lustre-discuss at lists.lustre.org; wc-discuss at whamcloud.com >> *Subject:* [Lustre-discuss] delete a "undeletable" file >> >> Hello, >> I have a corrupt file than I can?t delete. >> This is my file: >>> ls ?la .viminfo >> /-????????? ? ? ? ? ? .viminfo/ >> />lfs getstripe .viminfo/ >> /.viminfo/ >> /lmm_stripe_count: 6/ >> /lmm_stripe_size: 1048576/ >> /lmm_layout_gen: 0/ >> /lmm_stripe_offset: 18/ >> /obdidx objid objid group/ >> /18 1442898 0x160452 0/ >> /22 48 0x30 0/ >> /19 1442770 0x1603d2 0/ >> /21 49 0x31 0/ >> /23 48 0x30 0/ >> /20 50 0x32 0/ >> And these are my OST: >> />lctl dl/ >> /0 UP mgc MGC192.168.11.9 at tcp f6d5b76f-a7e0-61ca-b389-cb3896b86186 5/ >> /1 UP lov cetafs-clilov-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 4/ >> /2 UP lmv cetafs-clilmv-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 4/ >> /3 UP mdc cetafs-MDT0000-mdc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /4 UP osc cetafs-OST0000-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /5 UP osc cetafs-OST0001-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /6 UP osc cetafs-OST0002-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /7 UP osc cetafs-OST0003-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /8 UP osc cetafs-OST0004-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /9 UP osc cetafs-OST0005-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /10 UP osc cetafs-OST0006-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /11 UP osc cetafs-OST0007-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /12 UP osc cetafs-OST0012-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /13 UP osc cetafs-OST0013-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /14 UP osc cetafs-OST0008-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /15 UP osc cetafs-OST000a-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /16 UP osc cetafs-OST0009-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /17 UP osc cetafs-OST000b-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /18 UP osc cetafs-OST000c-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /19 UP osc cetafs-OST000d-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /20 UP osc cetafs-OST000e-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /21 UP osc cetafs-OST000f-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /22 UP osc cetafs-OST0010-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /23 UP osc cetafs-OST0011-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /24 UP osc cetafs-OST0018-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /25 UP osc cetafs-OST0015-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /26 UP osc cetafs-OST0016-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /27 UP osc cetafs-OST0017-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> When I try to delete the file I got the next menssage: >> /> rm .viminfo/ >> /rm: cannot remove `.viminfo'': Invalid argument/ >> How can I do to delete the file? >> THANKS! >> >> // >> >> // >> >> // >> >> // >> >> /Alfonso Pardo D?az >> /*/Researcher / System Administrator at CETA-Ciemat /* >> /c/ Sola n? 1; 10200 Trujillo, ESPA?A/ >> /Tel: +34 927 65 93 17 Fax: +34 927 32 32 37/ >> >> CETA-Ciemat logo <http://www.ceta-ciemat.es/> >> >> ---------------------------- Confidencialidad: Este mensaje y sus >> ficheros adjuntos se dirige exclusivamente a su destinatario y puede >> contener informaci?n privilegiada o confidencial. Si no es vd. el >> destinatario indicado, queda notificado de que la utilizaci?n, >> divulgaci?n y/o copia sin autorizaci?n est? prohibida en virtud de la >> legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos >> que nos lo comunique inmediatamente respondiendo al mensaje y proceda >> a su destrucci?n. Disclaimer: This message and its attached files is >> intended exclusively for its recipients and may contain confidential >> information. If you received this e-mail in error you are hereby >> notified that any dissemination, copy or disclosure of this >> communication is strictly prohibited and may be unlawful. In this >> case, please notify us by a reply and delete this email and its >> contents immediately. ---------------------------- >> >> >> _______________________________________________ >> Lustre-discuss mailing list >> Lustre-discuss at lists.lustre.org >> http://lists.lustre.org/mailman/listinfo/lustre-discuss > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss
If I run "unlink .viminfo" I got the same error: unlink: cannot unlink `.viminfo'': Invalid argument I can''t stop the MDS/OSS to do a lfsck or e2fsck because is a filesystem in production of a lots of "terabytes" Any idea more to delete the "damm file"? THANKS! -----Mensaje original----- From: Bob Ball Sent: Thursday, March 07, 2013 6:09 PM To: Colin Faber Cc: Alfonso Pardo ; Ben Evans ; lustre-discuss at lists.lustre.org Subject: Re: [Lustre-discuss] delete a "undeletable" file You could just unlink it instead. That will work when rm fails. bob On 3/7/2013 11:10 AM, Colin Faber wrote:> Hi, > > If the file is disassociated with an OST which is offline, bring the OST > back online, if the OST object it self is missing then you can remove > the file using ''unlink'' rather than ''rm'' to unlink the object meta data. > > If you want to try and recover the missing OST object an lfs getstripe > against the file should yield the the OST on which it resides. Once > that''s determined you can take that OST offline and e2fsck may > successfully restore it. > > Another option as Ben correctly points out, lfsck will correct / prune > this meta data as well as the now orphaned (if any) OST object. > > -cf > > > On 03/07/2013 08:30 AM, Ben Evans wrote: >> The snarky reply would be to use Emacs. >> >> More seriously: >> >> When I see something like ?????? in the attributes for a file, my >> first thought is that the group_upcall on the filesystem is not >> correct, so permissions are broken. If you can log on as root, you may >> be able to see it clearly. >> >> If that doesn''t work, you may have to run an fsck on the MDT (which >> may take minutes to hours depending on the size of your MDT) >> >> If that doesn''t work, follow the procedure for running an lfsck (which >> will take a long time, and require quite a bit of storage to execute) >> >> -Ben Evans >> >> ------------------------------------------------------------------------ >> *From:* lustre-discuss-bounces at lists.lustre.org >> [lustre-discuss-bounces at lists.lustre.org] on behalf of Alfonso Pardo >> [alfonso.pardo at ciemat.es] >> *Sent:* Thursday, March 07, 2013 10:09 AM >> *To:* lustre-discuss at lists.lustre.org; wc-discuss at whamcloud.com >> *Subject:* [Lustre-discuss] delete a "undeletable" file >> >> Hello, >> I have a corrupt file than I can?t delete. >> This is my file: >>> ls ?la .viminfo >> /-????????? ? ? ? ? ? .viminfo/ >> />lfs getstripe .viminfo/ >> /.viminfo/ >> /lmm_stripe_count: 6/ >> /lmm_stripe_size: 1048576/ >> /lmm_layout_gen: 0/ >> /lmm_stripe_offset: 18/ >> /obdidx objid objid group/ >> /18 1442898 0x160452 0/ >> /22 48 0x30 0/ >> /19 1442770 0x1603d2 0/ >> /21 49 0x31 0/ >> /23 48 0x30 0/ >> /20 50 0x32 0/ >> And these are my OST: >> />lctl dl/ >> /0 UP mgc MGC192.168.11.9 at tcp f6d5b76f-a7e0-61ca-b389-cb3896b86186 5/ >> /1 UP lov cetafs-clilov-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 4/ >> /2 UP lmv cetafs-clilmv-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 4/ >> /3 UP mdc cetafs-MDT0000-mdc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /4 UP osc cetafs-OST0000-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /5 UP osc cetafs-OST0001-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /6 UP osc cetafs-OST0002-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /7 UP osc cetafs-OST0003-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /8 UP osc cetafs-OST0004-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /9 UP osc cetafs-OST0005-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /10 UP osc cetafs-OST0006-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /11 UP osc cetafs-OST0007-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /12 UP osc cetafs-OST0012-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /13 UP osc cetafs-OST0013-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /14 UP osc cetafs-OST0008-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /15 UP osc cetafs-OST000a-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /16 UP osc cetafs-OST0009-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /17 UP osc cetafs-OST000b-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /18 UP osc cetafs-OST000c-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /19 UP osc cetafs-OST000d-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /20 UP osc cetafs-OST000e-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /21 UP osc cetafs-OST000f-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /22 UP osc cetafs-OST0010-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /23 UP osc cetafs-OST0011-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /24 UP osc cetafs-OST0018-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /25 UP osc cetafs-OST0015-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /26 UP osc cetafs-OST0016-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> /27 UP osc cetafs-OST0017-osc-ffff88009816e400 >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ >> When I try to delete the file I got the next menssage: >> /> rm .viminfo/ >> /rm: cannot remove `.viminfo'': Invalid argument/ >> How can I do to delete the file? >> THANKS! >> >> // >> >> // >> >> // >> >> // >> >> /Alfonso Pardo D?az >> /*/Researcher / System Administrator at CETA-Ciemat /* >> /c/ Sola n? 1; 10200 Trujillo, ESPA?A/ >> /Tel: +34 927 65 93 17 Fax: +34 927 32 32 37/ >> >> CETA-Ciemat logo <http://www.ceta-ciemat.es/> >> >> ---------------------------- Confidencialidad: Este mensaje y sus >> ficheros adjuntos se dirige exclusivamente a su destinatario y puede >> contener informaci?n privilegiada o confidencial. Si no es vd. el >> destinatario indicado, queda notificado de que la utilizaci?n, >> divulgaci?n y/o copia sin autorizaci?n est? prohibida en virtud de la >> legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos >> que nos lo comunique inmediatamente respondiendo al mensaje y proceda >> a su destrucci?n. Disclaimer: This message and its attached files is >> intended exclusively for its recipients and may contain confidential >> information. If you received this e-mail in error you are hereby >> notified that any dissemination, copy or disclosure of this >> communication is strictly prohibited and may be unlawful. In this >> case, please notify us by a reply and delete this email and its >> contents immediately. ---------------------------- >> >> >> _______________________________________________ >> Lustre-discuss mailing list >> Lustre-discuss at lists.lustre.org >> http://lists.lustre.org/mailman/listinfo/lustre-discuss > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss
You can move the entire folder (mv) to another location /lustre_fs/somthing/badfiles recreate the folder and mv back only the good files.> If I run "unlink .viminfo" I got the same error: > > unlink: cannot unlink `.viminfo'': Invalid argument > > > I can''t stop the MDS/OSS to do a lfsck or e2fsck because is a filesystem in > production of a lots of "terabytes" > > > Any idea more to delete the "damm file"? > > > > THANKS! > > -----Mensaje original----- > From: Bob Ball > Sent: Thursday, March 07, 2013 6:09 PM > To: Colin Faber > Cc: Alfonso Pardo ; Ben Evans ; lustre-discuss at lists.lustre.org > Subject: Re: [Lustre-discuss] delete a "undeletable" file > > You could just unlink it instead. That will work when rm fails. > > bob > > On 3/7/2013 11:10 AM, Colin Faber wrote: > > Hi, > > > > If the file is disassociated with an OST which is offline, bring the OST > > back online, if the OST object it self is missing then you can remove > > the file using ''unlink'' rather than ''rm'' to unlink the object meta data. > > > > If you want to try and recover the missing OST object an lfs getstripe > > against the file should yield the the OST on which it resides. Once > > that''s determined you can take that OST offline and e2fsck may > > successfully restore it. > > > > Another option as Ben correctly points out, lfsck will correct / prune > > this meta data as well as the now orphaned (if any) OST object. > > > > -cf > > > > > > On 03/07/2013 08:30 AM, Ben Evans wrote: > >> The snarky reply would be to use Emacs. > >> > >> More seriously: > >> > >> When I see something like ?????? in the attributes for a file, my > >> first thought is that the group_upcall on the filesystem is not > >> correct, so permissions are broken. If you can log on as root, you may > >> be able to see it clearly. > >> > >> If that doesn''t work, you may have to run an fsck on the MDT (which > >> may take minutes to hours depending on the size of your MDT) > >> > >> If that doesn''t work, follow the procedure for running an lfsck (which > >> will take a long time, and require quite a bit of storage to execute) > >> > >> -Ben Evans > >> > >> ------------------------------------------------------------------------ > >> *From:* lustre-discuss-bounces at lists.lustre.org > >> [lustre-discuss-bounces at lists.lustre.org] on behalf of Alfonso Pardo > >> [alfonso.pardo at ciemat.es] > >> *Sent:* Thursday, March 07, 2013 10:09 AM > >> *To:* lustre-discuss at lists.lustre.org; wc-discuss at whamcloud.com > >> *Subject:* [Lustre-discuss] delete a "undeletable" file > >> > >> Hello, > >> I have a corrupt file than I can?t delete. > >> This is my file: > >>> ls ?la .viminfo > >> /-????????? ? ? ? ? ? .viminfo/ > >> />lfs getstripe .viminfo/ > >> /.viminfo/ > >> /lmm_stripe_count: 6/ > >> /lmm_stripe_size: 1048576/ > >> /lmm_layout_gen: 0/ > >> /lmm_stripe_offset: 18/ > >> /obdidx objid objid group/ > >> /18 1442898 0x160452 0/ > >> /22 48 0x30 0/ > >> /19 1442770 0x1603d2 0/ > >> /21 49 0x31 0/ > >> /23 48 0x30 0/ > >> /20 50 0x32 0/ > >> And these are my OST: > >> />lctl dl/ > >> /0 UP mgc MGC192.168.11.9 at tcp f6d5b76f-a7e0-61ca-b389-cb3896b86186 5/ > >> /1 UP lov cetafs-clilov-ffff88009816e400 > >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 4/ > >> /2 UP lmv cetafs-clilmv-ffff88009816e400 > >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 4/ > >> /3 UP mdc cetafs-MDT0000-mdc-ffff88009816e400 > >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > >> /4 UP osc cetafs-OST0000-osc-ffff88009816e400 > >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > >> /5 UP osc cetafs-OST0001-osc-ffff88009816e400 > >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > >> /6 UP osc cetafs-OST0002-osc-ffff88009816e400 > >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > >> /7 UP osc cetafs-OST0003-osc-ffff88009816e400 > >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > >> /8 UP osc cetafs-OST0004-osc-ffff88009816e400 > >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > >> /9 UP osc cetafs-OST0005-osc-ffff88009816e400 > >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > >> /10 UP osc cetafs-OST0006-osc-ffff88009816e400 > >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > >> /11 UP osc cetafs-OST0007-osc-ffff88009816e400 > >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > >> /12 UP osc cetafs-OST0012-osc-ffff88009816e400 > >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > >> /13 UP osc cetafs-OST0013-osc-ffff88009816e400 > >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > >> /14 UP osc cetafs-OST0008-osc-ffff88009816e400 > >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > >> /15 UP osc cetafs-OST000a-osc-ffff88009816e400 > >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > >> /16 UP osc cetafs-OST0009-osc-ffff88009816e400 > >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > >> /17 UP osc cetafs-OST000b-osc-ffff88009816e400 > >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > >> /18 UP osc cetafs-OST000c-osc-ffff88009816e400 > >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > >> /19 UP osc cetafs-OST000d-osc-ffff88009816e400 > >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > >> /20 UP osc cetafs-OST000e-osc-ffff88009816e400 > >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > >> /21 UP osc cetafs-OST000f-osc-ffff88009816e400 > >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > >> /22 UP osc cetafs-OST0010-osc-ffff88009816e400 > >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > >> /23 UP osc cetafs-OST0011-osc-ffff88009816e400 > >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > >> /24 UP osc cetafs-OST0018-osc-ffff88009816e400 > >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > >> /25 UP osc cetafs-OST0015-osc-ffff88009816e400 > >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > >> /26 UP osc cetafs-OST0016-osc-ffff88009816e400 > >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > >> /27 UP osc cetafs-OST0017-osc-ffff88009816e400 > >> a7ba6783-6ed8-2197-4ffc-fecbff9860a5 5/ > >> When I try to delete the file I got the next menssage: > >> /> rm .viminfo/ > >> /rm: cannot remove `.viminfo'': Invalid argument/ > >> How can I do to delete the file? > >> THANKS! > >> > >> // > >> > >> // > >> > >> // > >> > >> // > >> > >> /Alfonso Pardo D?az > >> /*/Researcher / System Administrator at CETA-Ciemat /* > >> /c/ Sola n? 1; 10200 Trujillo, ESPA?A/ > >> /Tel: +34 927 65 93 17 Fax: +34 927 32 32 37/ > >> > >> CETA-Ciemat logo <http://www.ceta-ciemat.es/> > >> > >> ---------------------------- Confidencialidad: Este mensaje y sus > >> ficheros adjuntos se dirige exclusivamente a su destinatario y puede > >> contener informaci?n privilegiada o confidencial. Si no es vd. el > >> destinatario indicado, queda notificado de que la utilizaci?n, > >> divulgaci?n y/o copia sin autorizaci?n est? prohibida en virtud de la > >> legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos > >> que nos lo comunique inmediatamente respondiendo al mensaje y proceda > >> a su destrucci?n. Disclaimer: This message and its attached files is > >> intended exclusively for its recipients and may contain confidential > >> information. If you received this e-mail in error you are hereby > >> notified that any dissemination, copy or disclosure of this > >> communication is strictly prohibited and may be unlawful. In this > >> case, please notify us by a reply and delete this email and its > >> contents immediately. ---------------------------- > >> > >> > >> _______________________________________________ > >> Lustre-discuss mailing list > >> Lustre-discuss at lists.lustre.org > >> http://lists.lustre.org/mailman/listinfo/lustre-discuss > > _______________________________________________ > > Lustre-discuss mailing list > > Lustre-discuss at lists.lustre.org > > http://lists.lustre.org/mailman/listinfo/lustre-discuss > > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss >