From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Date: Thu, 17 Dec 2015 18:05:43 +0100 Message-ID: From: Ole-Hjalmar Kristensen To: 9fans@9fans.net Content-Type: multipart/alternative; boundary=001a114432127a072405271b08d7 Subject: [9fans] Migration of vac score to fossil Topicbox-Message-UUID: 7a9d2568-ead9-11e9-9d60-3106f5b1d025 --001a114432127a072405271b08d7 Content-Type: text/plain; charset=UTF-8 I have a file server running Linux at home, with a normal ext3 file system and a plan9port venti. I use this venti for vac backup of both the ext3 file system and other Linux boxes. However, the 2 TB ext3 is running out of space, while the venti is roughly 50% full. I could just buy a bigger disk, of course, but the exit3 itself is mainly an archive (pictures, video, and many years of accumulated documents and software), so I consider switching to a fossil+venti file server instead. The fossil manual says "The score should have been generated by fossil rather than by vac, so that the appropriate snapshot metadata is present". Is there any way of coercing fossil to initialize itself properly from a score produced by vac? I could copy the files from ext3, but would likely run out of space in fossil, which I gather is a bad idea. I run a 9front cwfs auth/cpu/file server, but have no experience with fossil, so any help is welcome. --001a114432127a072405271b08d7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I have a file server running Linux at home, with a normal = ext3 file system and a plan9port venti. I use this venti for vac backup of = both the ext3 file system and other Linux boxes. However, the 2 TB ext3 is = running out of space, while the venti is roughly 50% full. I could just buy= a bigger disk, of course, but the exit3 itself is mainly an archive (pictu= res, video, and many years of accumulated documents and software), so I con= sider switching to a fossil+venti file server instead. The fossil manual sa= ys "The score should have been generated by fossil rather than by vac,= so that the appropriate snapshot metadata is present". Is there any w= ay of coercing fossil to initialize itself properly from a score produced b= y vac? I could copy the files from ext3, but would likely run out of space = in fossil, which I gather is a bad idea. I run a 9front cwfs auth/cpu/file = server, but have no experience with fossil, so any help is welcome.

=20
=20
=20
=20
--001a114432127a072405271b08d7--