see which issues have been reported (fun)
                     page last updated on Tue Apr 24 11:20:30 CEST 2007

      update: as of 24-04-2007, all the diffs in this page had been committed
      to openbsd's cvs tree. rejoice!

      the diffs below add ffs2 functionality to openbsd. with them, you should
      be able to create, check, mount and unmount ffs2 volumes. manipulation of
      volumes bigger than one terabyte is not possible yet, due to disklabel
      limitations (which are being worked on).

      you don't have to apply all of them, but they must be applied in order.
      it is *very* important to test each diff, since that is how they are
      going to be committed. things to make sure are:

      - that a new fsck is able to parse an old file system;
      - that an old fsck is able to parse a new file system;
      - that both new/old fsck are happy with an old/new file system mounted
        (and then unmounted, of course) using a old/new kernel;
      - that newfs produces a file system which can be parsed by old/new fsck;
      - that ffs2 file systems can be created, mounted and checked!

      softdep should work. please make sure you have extremely current sources.
      breakage should be reported to pedro@openbsd.org, thanks!

      first diff (54k, sha1 531b40e337d5b0200638e897b45b9a80a678f8b8)

      what does it do?

          - adds new ffs2 fields to the superblock
          - changes file system tools to keep accessing ffs1 fields

      will i lose all my pr0n?

          unlikely.

      any special steps in applying it?

          compile a kernel first, do a 'make includes', then a build. if you
          plan to mount FFS2 volumes, the kernel must be compiled with 'option
          FFS2'.

      second diff(32k, sha1 92f2b905d084f5c4199c2fef777e2005e02f5e9a)

      what does it do?

          cleans up newfs

      will i lose all my pr0n?

          unlikely.

      any special steps in applying it?

          no, just recompile and install newfs.

      third diff (50k, sha1 632c7f92be73fbd91461f173e4324fe25fd62f5c)

      what does it do?

          makes newfs able to generate ffs2 file systems

      will i lose all my pr0n?

          maybe.

      any special steps in applying it?

          no, just recompile and install newfs.

      fourth diff (60k, sha1 08c4c5db2eb32795f3da1491bc548b38cef2fe54)

      what does it do?

          makes fsck able to parse ffs2 file systems

      will i lose all my pr0n?

          you betcha. :-)

      any special steps in applying it?

          no, just recompile and install fsck.

      fifth diff (6k, sha1 50f3373c4df0025de80a3158c0f1f1aefe3c6f98)

      what does it do?

          makes fsirand able to operate on ffs2 file systems

      will i lose all my pr0n?

          unlikely.

      any special steps in applying it?

          no, just recompile and install fsirand.

      final notes

          rejoice!

          i'm a smartass and i noticed you did not port the other file systems
          tools to ffs2 yet. when will that happen?

              as soon as i get enough testing reports on these diffs

      issues found

          summary                                 diff who     fixed
          warning about 'ffs' symbol in newfs     2nd  ckuethe yes
          fsdb doesn't compile anymore            3rd  ckuethe yes
          fsck dumps core on 1 terabyte partition 3rd  ckuethe yes
          'ffs_checkblk: bad block' panic w/ ffs2 1st  simon   yes
          mfs doesn't work anymore                3rd  thib    yes
          'bad inode number 0 to ginode' in fsck  4th  thib    yes
          fsck dumps core on ffs2 partition       4th  thib    yes
          ffs2 on old ffs1 confuses the kernel    3rd  martin  yes