From: Fabrizio Cuseo <f.cuseo@panservice.it>
To: Dietmar Maurer <dietmar@proxmox.com>
Cc: pbs-devel <pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] Problem with PBS and old CentOS 4.9 vm
Date: Tue, 25 Aug 2020 17:18:31 +0200 (CEST) [thread overview]
Message-ID: <40489559.79435.1598368711511.JavaMail.zimbra@zimbra.panservice.it> (raw)
In-Reply-To: <756044694.61.1598368328815@webmail.proxmox.com>
Yes, I am making a lot of tests, and with a vanilla 4.9 centOS i don't have the problem.
But the strange is that with the old (full) pve backup, i have no problems.
I use ext3 filesystem (not xfs).
Now I am trying to rsync the old content to a new vm (rsync /) so the filesystem descriptors are new, but the content is the old one.
Thanks, Fabrizio
PS: i am using for test a vm with pbs, and for repository a MooseFS filesystem with 120Tbyte.
----- Il 25-ago-20, alle 17:12, Dietmar Maurer dietmar@proxmox.com ha scritto:
>> I have a problem with a 4.9 centOS vm. If i restore after backup, during the
>> initial FSCK there are a lot of errors and filesystem problems.
>>
>> I have tried to:
>> - change disk from virtio to IDE
>> - backup with vm off
>> - make fsck, stop the vm, backup, and restore
>>
>> If i backup the vm powered off, when I restore it, no fsck is prompted at boot,
>> but if I reset (without any activity) the vm, again the filesystem is full of
>> errors.
>> If I reset the original VM, no problem during fsck at boot.
>>
>> If i fix the restored vm, I backup it again (powered on or off), same problem.
>>
>> So seems the the problem is making and restoring backup.
>>
>> No problem with a centOS 6.X (i am testing other OS versions).
>>
>> Some idea ?
>
> file system on centos 4.9 is buggy (old xfs version)?
next prev parent reply other threads:[~2020-08-25 15:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 14:22 Fabrizio Cuseo
2020-08-25 15:12 ` Dietmar Maurer
2020-08-25 15:18 ` Fabrizio Cuseo [this message]
2020-08-26 12:26 ` Fabrizio Cuseo
2020-08-31 7:07 ` Fabian Ebner
2020-08-31 7:13 ` Fabrizio Cuseo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40489559.79435.1598368711511.JavaMail.zimbra@zimbra.panservice.it \
--to=f.cuseo@panservice.it \
--cc=dietmar@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.