On Thu, Mar 18, 2004 at 07:07:45PM -0500, Gregory (Grisha) Trubetskoy wrote:
>
> OK, I figured it out.
>
> I guess it really helps not to have CONFIG_INOXID_NONE in the kernel
> config. (Or in other words "Persistent Context ID for files" options in
> make menuconfig).
LOL!
> Sorry for the conf
OK, I figured it out.
I guess it really helps not to have CONFIG_INOXID_NONE in the kernel
config. (Or in other words "Persistent Context ID for files" options in
make menuconfig).
Sorry for the confusion!
Grisha
On Thu, 18 Mar 2004, Herbert Poetzl wrote:
> On Thu, Mar 18, 2004 at 04:08:43PM
On Thu, 18 Mar 2004, Herbert Poetzl wrote:
> saving the 'current' value on vserver stop and restoring it on vserver
> start should be sufficient ...
I guess I'm confused as to whether mounting the filesystem with tagctx is
sufficient. I'm on 1.26 (so I don't have lsxid), and I was following
inst
On Thu, Mar 18, 2004 at 04:08:43PM -0500, Gregory (Grisha) Trubetskoy wrote:
>
> Is there a way to preserve the cq hash across reboots?
>
> I saw the script that someone e-mail that preserves the amount of space
> available, but what about the hash itself?
>
> Otherwise it looks like if you dele
Is there a way to preserve the cq hash across reboots?
I saw the script that someone e-mail that preserves the amount of space
available, but what about the hash itself?
Otherwise it looks like if you delete any files that you created prior to
reboot you don't gain any space back.
Or am I missi
