Hello! So our ISPConfig decided to go nuts with many errors (Listed below). Just thought that maybe pointing the save location of mails would quickly resolve the issue instead of doing an xfs_repair. I've previously used the process provided here https://www.howtoforge.com/use_moun...ctory_of_a_ispconfig_server_to_a_new_location when we ran out of disk space but this was on the same disk, different partition (currently having errors). I've just added a new disk to the VM and would like to point vmail there. Do I use the same procedure? Any advise would be greatly appreciated ERRORS dmesg Internal Error XFS_WANT_CORRUPTED_RETURN at line 353 of file fs/xfs/libxfs/xfs_alloc.c caller xfs_alloc_ag_vextent_near+0x796/0xac0 [xfs] AND on maillog: Sep 4 05:55:09 mail dovecot: lda([email protected]): Error: open(/var/vmail/domain.com/ian/Maildir/tmp/1725400509.M666948P16889.mail.domain.com) failed: Structure needs cleaning Sep 4 05:55:09 mail dovecot: lda([email protected]): Error: sieve: msgid=<CAOxWGL7SAVQ3Vdrrw8dbUoxhHQ4S5p5uPrvSgg1N+TOQVHNrhw@mail.gmail.com>: failed to store into mailbox 'INBOX': Internal error occurred. Refer to server log for more information. [2024-09-04 05:55:09] Sep 4 05:55:09 mail dovecot: lda([email protected]): Error: sieve: failed to open logfile (LOGGING TO STDERR): open(/var/vmail/domain.com/ian/.sieve.log) failed: Structure needs cleaning Sep 4 05:55:09 mail dovecot: lda([email protected]): Error: sieve: execution of script /var/vmail/domain.com/ian/.sieve;name=main script was aborted due to temporary failure (user logfile /var/vmail/domain.com/ian/.sieve.log may reveal additional details) Sep 4 05:55:09 mail postfix/pipe[16888]: 95D3740BEC4A: to=<[email protected]>, relay=dovecot, delay=0.11, delays=0.01/0.03/0/0.07, dsn=4.3.0, status=deferred (temporary failure. Command output: sieve: info: started log at Sep 04 05:55:09. error: msgid=<CAOxWGL7SAVQ3Vdrrw8dbUoxhHQ4S5p5uPrvSgg1N+TOQVHNrhw@mail.gmail.com>: failed to store into mailbox 'INBOX': Internal error occurred. Refer to server log for more information. [2024-09-04 05:55:09]. )
No this is a XFS filesystem use the xfs-utils. You should unmount the filesystem if it is mounted. Then first check with: Code: xfs_check <device> After that run the repair: Code: xfs_repair <device> If the filesystem is still unmountable afterwards you can try to repair it with log zeroing option like this: Code: xfs_repair -L <device>
