| Re: fsck of simfs [message #47709 is a reply to message #47708] |
Wed, 29 August 2012 08:10  |
Corin Langosch
Messages: 18
Registered: March 2012
|
Junior Member |
|
|
Hi Vasily,
yes. Ploop creates a new block device on which you then create a new fs.
Corin
On 29.08.2012 at 09:41 +0200, Rene C. <openvz@dokbua.com> wrote:
> Thanks everybody. Hm, that's a bit of a bummer.
>
> Would using ploop fs change that? (I mean, I understand it won't fix
> the present problem but for the future)
>
>
> On Wed, Aug 29, 2012 at 2:06 PM, Vasily Averin <vvs@parallels.com
> <mailto:vvs@parallels.com>> wrote:
>
> Dear Rene,
>
> simfs is a proxy-filesystem.
> you need to stop all containers and check file-system on
> underlying device (ext4 on /vz ?)
>
> thank you,
> Vasily Averin
>
> On 08/29/2012 10:37 AM, Rene C. wrote:
> >
> > I suspect there may be some filesystem corruption in a VE. Is
> it possible to fsck the simfs filesystem for a single container
> somehow, or do I need to stop all containers on the hardware node
> partition partition holding the simfs in order to check the
> filesystem?
> > _______________________________________________
> > Users mailing list
> > Users@openvz.org <mailto:Users@openvz.org>
> > https://openvz.org/mailman/listinfo/users
> >
>
>
>
>
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
