[Oberon] FPGA - Save / Restore OBERON.FS

[Chris Burrows]

Hi Tomas,

It might be very fast but you risk not saving enough sectors to include all
of your data. Any time that you save now will be well outweighed by the time
you lose later if and when you find that parts of some of your files are
missing.

Read Chapter 7 'The file system' of the Project Oberon documentation to
learn how the sector allocation system has been designed. 

The number of sectors returned by System.Watch appears to be the number of
sectors currently allocated. What you need to do if you want to backup the
Oberon partition is save all sectors up to and including the *highest* one
that is currently allocated. This will be a higher value than the number of
sectors allocated if some of the intervening sectors are currently unused. 

I initially had a similar problem with partial backups which is why I now
err on the safe side and backup the whole partition.

Regards,
Chris Burrows

CFB Software
http://www.astrobe.com/RISC5

> -----Original Message-----
> From: Oberon [mailto:oberon-bounces at lists.inf.ethz.ch] On Behalf Of
> Tomas Kral
> Sent: Friday, 14 April 2017 5:20 PM
> To: Oberon@
> Subject: [Oberon] FPGA - Save / Restore OBERON.FS
> 
> Hi Christopher,
> 
> EDIT, need $((256*1024+1)), as it is 262144+1 where OBERON.FS starts
> and 1st block is not used, modulo 29.
> 
> I have in the end resorted to:
> $ dd if=/dev/sdc of=OBERON1.FS bs=1K skip=$((256*1024+1)) count=65K
> 
> `System.Watch' reports 921 sectors used, so I tempted to try $ dd
> if=/dev/sdc of=OBERON1.FS bs=1K skip=$((256*1024+1)) count=921,
> instead.
> 
> Which goes very fast on RPI here.
> 
> Tomas
> --
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related
> systems https://lists.inf.ethz.ch/mailman/listinfo/oberon