November 2013 - HPDD-discuss

by Anthony Alba

I would like to change the NID on a 2.1.6 combined MGS/MDS but the 2.x isn't clear how to do this. The documentation describes what to do on a MDS. Is this necessary on a combined MGS/MDS? When the device is mounted, will it automatically acquire the new NID, since it is an MGS as well? ## mds-node$ tunefs.lustre --writeconf <device> mds-node$ tunefs.lustre --erase-param --mgsnode=<new_nid> --writeconf <device> -Anthony

7 years, 10 months

1
0
0 / 0

Are there binary files of Lustre 2.4.1 with zfs 6.2?

by Arman Khalatyan

Hi, Is it possible to upgrade zfs and spl on running lustre 2.4.1? thanks. Arman.

7 years, 10 months

1
1
0 / 0

Lustre 2.6 update - November 22nd 2013

by Jones, Peter A

Hi there Here is an update on the Lustre 2.6 release. Landings ======== -A number of landings made http://git.whamcloud.com/?p=fs/lustre-release.git;a=shortlog;h=refs/heads... Testing ======= -Testing on 2.5.51 tag is ongoing Blockers ======== -https://jira.hpdd.intel.com/issues/?jql=project%20%3D%20LU%20AND%20fixVersion%20%3D%20%22Lustre%202.6.0%22%20AND%20resolution%20%3D%20Unresolved%20AND%20priority%20%3D%20Blocker%20ORDER%20BY%20key%20DESC -If there are any issues not presently marked as blockers that you believe should be, please let me know Other ===== -Master is presently open for feature landings; feature freeze is January 31st Thanks Peter PS/ You can also keep up to date with matters relating to the 2.6 release on the CDWG wiki - http://wiki.opensfs.org/Lustre_2.6.0

7 years, 10 months

1
0
0 / 0

Re: [HPDD-discuss] [REVIEW] fix build of lustre without CONFIG_PROC_FS

by Dilger, Andreas

Doh! I should have looked at the patches more closely. I agree that if the patches are for the upstream client then sending them to Gerritt won't work. I'll review the patches and then they should be sent to Greg (staging tree maintainer). I'm trying to get a Gerritt instance that tracks the upstream kernel set up, so that we can accept patches there and have them tested. But for now Tao has been managing the upstream submission of patches via Github. Cheers, Andreas On 2013-11-17, at 22:32, "Drokin, Oleg" <oleg.drokin(a)intel.com> wrote: > Hello! > > The problem here is that the patches are for the client code in mainline kernel. > So I've been wondering myself how to get the two working together: our own tree and (somewhat different) mainline. > I don't think we would be able to route all patches traffic through our tree in any case. > > Bye, > Oleg > On Nov 18, 2013, at 2:11 PM, Dilger, Andreas wrote: > >> Hello Alexander, >> Thanks for sending in your patches. These are very timely fixes that we need for the upstream kernel code. >> >> Typically we review patches for Lustre using Gerritt, which allows us to track all of the review comments in one place, and also hooks into our automated testing system. >> >> Please see: >> https://wiki.hpdd.intel.com/display/PUB/Submitting+Changes >> >> Cheers, Andreas >> >> On 2013-11-16, at 15:56, "Alexander Beregalov" <a.beregalov(a)gmail.com> wrote: >> >>> Hi Andreas, Oleg, >>> >>> Could you review this bunch of patches. However it is not yet compilable, >>> more efforts are required. >

7 years, 11 months

1
0
0 / 0

Re: [HPDD-discuss] [REVIEW] fix build of lustre without CONFIG_PROC_FS

by Dilger, Andreas

Hello Alexander, Thanks for sending in your patches. These are very timely fixes that we need for the upstream kernel code. Typically we review patches for Lustre using Gerritt, which allows us to track all of the review comments in one place, and also hooks into our automated testing system. Please see: https://wiki.hpdd.intel.com/display/PUB/Submitting+Changes Cheers, Andreas On 2013-11-16, at 15:56, "Alexander Beregalov" <a.beregalov(a)gmail.com<mailto:a.beregalov@gmail.com>> wrote: Hi Andreas, Oleg, Could you review this bunch of patches. However it is not yet compilable, more efforts are required.

7 years, 11 months

1
0
0 / 0

Join OpenSFS at SC'13

by OpenSFS Administration

Hello Lustre community members, SC'13 is around the corner and we're looking forward to seeing you at this year's event! Be sure to mark your calendars to attend the Lustre related events and spread the word about these sessions - more details are below. Lustre related SC sessions: . SC'13 BoF Session: The Lustre Community - At the Intersection of HPC and Big Data o Tuesday, November 19th: 12:15-1:15pm in room(s) 405/406/407 o Speakers include: Jeff Layton, Intel; Paul Nowoczynski, DataDirect Networks; Shinji Sumimoto, Fujitsu; Sorin Fabish, EMC; Torben Kling Peterson, Xyratex; Eric Barton, Intel; Tommy Minyard, TACC, OpenSFS Community Board member . OpenSFS booth party - stop by to join us for drinks and meet others in the community! o Tuesday, November 19th: 4:00-6:00pm at the OpenSFS booth (#4125) . OpenSFS presentation: "Community Developed Scalable File Systems" o Wednesday, November 20th: 2:00-2:15pm at the Xyratex booth (#2107) o Tommy Minyard, OpenSFS Community Board member, TACC . OpenSFS presentation: "Community Involvement in the Lustre File System" o Wednesday, November 20th: 4:30-4:45pm at the DDN booth (#1307) o Chris Morrone, OpenSFS CDWG Chair, LLNL Interested in winning an iPad mini? Be sure to stop by the OpenSFS booth (#4125), or one of our participant booths, to pick up the OpenSFS passport. The passport is a fun way to interact with OpenSFS participants by collecting stamps from 7 participating booths. Return the completed passport to the OpenSFS booth for a chance to win your iPad mini! (Lustre not included.) Lastly, we encourage you to spread the word about the SC events planned for the Lustre community! More information is available on our <http://www.opensfs.org/events/sc13/> web site. We have also prepared the attached social media/website content for your marketing teams to use in promoting SC'13. We look forward to seeing you at SC'13 and encourage you to take advantage of the opportunities to join these events! Sincerely, OpenSFS Administration Open Scalable File Systems, Inc. is a strong and growing nonprofit organization dedicated to the success of the LustreR file system. OpenSFS was founded in 2010 to advance Lustre development, ensuring it remains vendor-neutral, open, and <http://lustre.opensfs.org/download-lustre/> free. Since its inception, OpenSFS has been responsible for advancing the Lustre file system and delivering <http://lustre.opensfs.org/community-lustre-roadmap/> new releases on behalf of the open source community. Through working groups, events, and ongoing funding initiatives, OpenSFS harnesses the power of collaborative development to fuel innovation and growth of the Lustre file system worldwide.

7 years, 11 months

1
0
0 / 0

Re: [HPDD-discuss] ldiskfs corruption

by Patrick Farrell

Vicky, You can upload large files to the Intel FTP server via anonymous FTP at: ftp.whamcloud.com Then there's a director called uploads, and you can either make an LU-3542 directory in there, or there may be one already. Then send the file name to the list or post it in LU-3542. - Patrick

7 years, 11 months

1
0
0 / 0

Lustre 2.6 update - November 8th 2013

by Jones, Peter A

Hi there Here is an update on the Lustre 2.6 release. Landings ======== -A number of landings made http://git.whamcloud.com/?p=fs/lustre-release.git;a=shortlog;h=refs/heads... Testing ======= -Testing on 2.5.51 tag underway Blockers ======== -https://jira.hpdd.intel.com/issues/?jql=project%20%3D%20LU%20AND%20fixVersion%20%3D%20%22Lustre%202.6.0%22%20AND%20resolution%20%3D%20Unresolved%20AND%20priority%20%3D%20Blocker%20ORDER%20BY%20key%20DESC -If there are any issues not presently marked as blockers that you believe should be, please let me know Other ===== -Master is presently open for feature landings; feature freeze is January 31st Thanks Peter PS/ You can also keep up to date with matters relating to the 2.6 release on the CDWG wiki - http://wiki.opensfs.org/Lustre_2.6.0

7 years, 11 months

1
0
0 / 0

Re: [HPDD-discuss] ldiskfs corruption

by Vicker, Darby (JSC-EG311)

That appears to have worked - thank you very much! I have the e2fsck and e2image output. I can post the former to the JIRA but the image is too big to upload to the JIRA as an attachment. Please email me if you want the image and I’ll send it to you via our file transfer service (I don’t have a good way to post it publicly). Darby > > Hi Darby, > > This looks similar LU-3542, I think it would be useful to get an image > of the filesystem for analysis as we only have one image and it's not as > damaged as yours. Can you do: > e2image -Q /dev/OSTnnnn OSTnnnn.qcow > bzip2 -9 OSTnnnn.qcow > > After you take the image, you can clean up the file system by creating a > debugfs script to unlink the files manually, it should look something like: > unlink /O/0/d4/3102500 > unlink /O/0/d2/3102690 > ...(1032 entries) > > You can parse it out from the 'has deleted/unused inode' messages in > e2fsck. Then it's a matter of doing debugfs -w -f <script> <dev>. > > HTH, > Kit > > --- > Kit Westneat > L3 Lustre Support, DDN > 703-659-3869 >

7 years, 11 months

1
0
0 / 0

ldiskfs corruption

by Vicker, Darby (JSC-EG311)

Hello, We have a corrupted OST that doesn’t seem to be in a repairable state. I’m looking for guidance on how to proceed. We are running lustre 2.1.6 on CentOS 6.4. The OST’s are built on a hardware RAID6. When the trouble started (yesterday) we unmounted the OST and did a verify on the RAID6 volume, which came back clean. Then ran an fsck, which found several problems. # e2fsck -fy /dev/Storage/ost0 e2fsck 1.42.7.wc1 (12-Apr-2013) hpfs2eg3-OST000b: recovering journal Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Entry '3102500' in /O/0/d4 (19398664) references inode 26072855 in group 203694 where _INODE_UNINIT is set. Fix? yes Entry '3102500' in /O/0/d4 (19398664) has an incorrect filetype (was 1, should be 0). Fix? yes Entry '3102690' in /O/0/d2 (19398662) references inode 26073045 in group 203695 where _INODE_UNINIT is set. Fix? yes Entry '3102690' in /O/0/d2 (19398662) has an incorrect filetype (was 1, should be 0). Fix? yes <cut - there were a total of 1024 of these> Restarting e2fsck from the beginning... One or more block group descriptor checksums are invalid. Fix? yes Group descriptor 203688 checksum is 0x3e34, should be 0x6fc3. FIXED. Group descriptor 203689 checksum is 0x492e, should be 0x18d9. FIXED. Group descriptor 203690 checksum is 0x8112, should be 0xd0e5. FIXED. Group descriptor 203691 checksum is 0x9b7c, should be 0xca8b. FIXED. Group descriptor 203692 checksum is 0xe010, should be 0xb1e7. FIXED. Group descriptor 203693 checksum is 0xf06f, should be 0xa198. FIXED. Group descriptor 203694 checksum is 0xc0ee, should be 0x9119. FIXED. Group descriptor 203695 checksum is 0xac6d, should be 0xfd9a. FIXED. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Entry '3102500' in /O/0/d4 (19398664) has deleted/unused inode 26072855. Clear? yes Entry '3102690' in /O/0/d2 (19398662) has deleted/unused inode 26073045. Clear? yes Entry '3102208' in /O/0/d0 (19398660) has deleted/unused inode 26072563. Clear? yes <cut - there are a total of 1032 of these> Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Inode bitmap differences: -(26072065--26073088) Fix? yes hpfs2eg3-OST000b: ***** FILE SYSTEM WAS MODIFIED ***** hpfs2eg3-OST000b: 2246277/28501376 files (4.4% non-contiguous), 1827729689/7296336896 blocks Remounting the OST doesn’t go well. Nov 7 07:39:01 hpfs2-eg3-oss11 kernel: LDISKFS-fs (dm-2): mounted filesystem with ordered data mode. Opts: Nov 7 07:39:02 hpfs2-eg3-oss11 kernel: LDISKFS-fs (dm-2): mounted filesystem with ordered data mode. Opts: Nov 7 07:39:02 hpfs2-eg3-oss11 kernel: Lustre: MGC10.148.0.142@o2ib: Reactivating import Nov 7 07:39:02 hpfs2-eg3-oss11 kernel: LustreError: 137-5: hpfs2eg3-OST000b: Not available for connect from 10.148.2.75@o2ib (not set up) Nov 7 07:39:02 hpfs2-eg3-oss11 kernel: Lustre: 11446:0:(ldlm_lib.c:2025:target_recovery_init()) RECOVERY: service hpfs2eg3-OST000b, 281 recoverable clients, last_transno 35381660 Nov 7 07:39:02 hpfs2-eg3-oss11 kernel: LustreError: 137-5: hpfs2eg3-OST000b: Not available for connect from 10.148.1.195@o2ib (not set up) Nov 7 07:39:02 hpfs2-eg3-oss11 kernel: Lustre: hpfs2eg3-OST000b: Now serving hpfs2eg3-OST000b/ on /dev/mapper/Storage-ost0 with recovery enabled Nov 7 07:39:45 hpfs2-eg3-oss11 kernel: Lustre: hpfs2eg3-OST000b: sending delayed replies to recovered clients Nov 7 07:39:45 hpfs2-eg3-oss11 kernel: Lustre: hpfs2eg3-OST000b: received MDS connection from 10.148.0.142@o2ib Nov 7 07:39:45 hpfs2-eg3-oss11 kernel: LDISKFS-fs error (device dm-2): ldiskfs_lookup: deleted inode referenced: 26072429 Nov 7 07:39:45 hpfs2-eg3-oss11 kernel: Aborting journal on device dm-2-8. Nov 7 07:39:45 hpfs2-eg3-oss11 kernel: LDISKFS-fs (dm-2): Remounting filesystem read-only Nov 7 07:39:45 hpfs2-eg3-oss11 kernel: LustreError: 11511:0:(filter.c:1506:filter_fid2dentry()) hpfs2eg3-OST000b: object 3102074:0 lookup error: rc -5 Nov 7 07:39:45 hpfs2-eg3-oss11 kernel: LustreError: 11511:0:(filter_lvb.c:105:filter_lvbo_init()) hpfs2eg3-OST000b: bad object 3102074/0: rc -5 Nov 7 07:39:45 hpfs2-eg3-oss11 kernel: LustreError: 11511:0:(ldlm_resource.c:1090:ldlm_resource_get()) lvbo_init failed for resource 3102074: rc -5 Nov 7 07:39:45 hpfs2-eg3-oss11 kernel: LustreError: 11590:0:(fsfilt-ldiskfs.c:382:fsfilt_ldiskfs_start()) error starting handle for op 8 (71 credits): rc -30 Nov 7 07:39:45 hpfs2-eg3-oss11 kernel: LustreError: 11588:0:(llog_cat.c:485:llog_cat_process_thread()) llog_cat_process() failed -30 Nov 7 07:39:45 hpfs2-eg3-oss11 kernel: LustreError: 11261:0:(fsfilt-ldiskfs.c:382:fsfilt_ldiskfs_start()) error starting handle for op 8 (106 credits): rc -30 Nov 7 07:39:45 hpfs2-eg3-oss11 kernel: LustreError: 11261:0:(filter.c:3588:filter_destroy_precreated()) error destroying precreate objid 6883425: -30 Nov 7 07:39:45 hpfs2-eg3-oss11 kernel: LustreError: 11261:0:(filter.c:3588:filter_destroy_precreated()) error destroying precreate objid 6883424: -30 Unmounting the OST and running the fsck again produces exactly the same output as before - a diff of the output shows no differences. Any idea why these problems aren’t being corrected by the fsck? Is there anything else I can try? Thanks, Darby

7 years, 11 months

2
1
0 / 0

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

HPDD-discuss November 2013