[Box Backup-dev] Re: [Box Backup] How to move boxbackup store
to a larger disk
Chris Wilson
boxbackup-dev@boxbackup.org
Sun, 14 Sep 2008 14:05:07 +0100 (BST)
Hi Ben,
On Sun, 14 Sep 2008, Ben Summers wrote:
> The container ID is set on the client side when the stored file is originally
> created.
Is it part of the file's header on the server then?
> It's not used for anything except store reconstruction, so it seemed
> a bit of a waste of time to update it when files were moved.
I guess if we had to use it for reconstruction, and it was wrong, then
we'd end up putting the file back into the wrong directory, or not knowing
where it should be at all?
> If it were to be changed, the server would have to do it, which given
> the restrictive RaidFile interface would require rewriting the file in
> it's entirety.
Can we fix the RaidFile interface? Especially as actual 3-stripe RAID is
going away, we could make this a no-op on 3-stripe RAID and trivial on
non-RAID?
> Maybe a reasonable solution is to simply remove that "warning"?
If it's too hard to actually repair the problem then I fully support doing
that to ease needless user fears.
Cheers, Chris.
--
_____ __ _
\ __/ / ,__(_)_ | Chris Wilson <0000 at qwirx.com> - Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Ruby/Perl/SQL Developer |
\ _/_/_/_//_/___/ | We are GNU : free your mind & your software |