Re: [lustre-discuss] Filesystem could not mount after e2fsck

2023-03-06 Thread Stephane Thiell via lustre-discuss
Hi Robin, Your MDT configuration file seems corrupt somehow. Those "already exists, won't add” errors make me think about a ticket we opened a while back https://jira.whamcloud.com/browse/LU-15000 It was also with 2.12 but only because we had used lctl llog_cancel (or the newer lctl del_ost

Re: [lustre-discuss] Filesystem could not mount after e2fsck

2023-03-06 Thread Teeninga, Robin via lustre-discuss
Hello Stephane, Thanks for your feedback. Why did you run e2fsck? I was suspecting some errors but the e2fsck didn't see anything Did e2fsck fix something? no What version of e2fsprogs are you using? e2fsprogs-1.46.2.wc3-0.el7.x86_64 The device had no free i-nodes anymore so I mounted the

Re: [lustre-discuss] Filesystem could not mount after e2fsck

2023-03-04 Thread Stephane Thiell via lustre-discuss
Hi Robin, Sorry to hear about your problem. A few questions… Why did you run e2fsck? Did e2fsck fix something? What version of e2fsprogs are you using? errno 28 is ENOSPC, what does dumpe2fs say about available space? You can check the values of "Free blocks” and "Free inodes” using this

[lustre-discuss] Filesystem could not mount after e2fsck

2023-03-02 Thread Teeninga, Robin via lustre-discuss
Hello, I've did an e2fsck on my MDT and after that I could not mount the MDT anymore It gives me this error when I've tried to mount the filesystem any ideas how to resolve this? We are running Lustre server 2.12.7 on CentOS 7.9 mount.lustre: mount /dev/mapper/-MDT at