headers
Dario Goldfarb | 1 Aug 2003 03:27

Mirroring 2 hard disks by soft for high availability

Hi,
    Im trying to mirror two disks to accomplish high availability on FreeBSD
4.8-RELEASE.
    I've configured Vinum with the following configuration :

    drive d1 device /dev/ad0s1e
    drive d1 device /dev/ad2s1f
    volume mirror setupstate
        plex org concat
            sd length 32g drive d1
        plex org concat
            sd length 32g drive d2

    This is working fine I have a 32 gb partition mounted on /data
    I think this should be writing the data on both partitions, right ?

    The problem is that when i take off the secondary disk to ensure that on
a disk failing it will keep on working, it dies with a kernel panic after
booting (right after the login screen). can anyone tell me what im doing
wrong ?

Thanks a lot in advance
Dario Goldfarb.

_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"
(Continue reading)

Permalink | Reply | 0 comments |
headers
Erez Zadok | 3 Aug 2003 03:59
Picon
Favicon

fistgen-0.0.7 released (stackable file systems)

We've released fistgen-0.0.7.  This includes new features, lots of bug fixes
for stability (esp. to Linux templates), and new FreeBSD 4.x/5.0 ports.

Get the new tarball from

	ftp://ftp.filesystems.org/pub/fist/fistgen-0.0.7.tar.gz

Here's the relevant portion of the NEWS file:

*** Notes specific to fistgen 0.0.7:

Major new features and changes:

- FreeBSD-5: A totally new port of stackable templates for FreeBSD 5.0.
  Verified with base0fs, wrapfs, and cryptfs using a large compile build,
  fsx, and our own home-brewed tools.

- FreeBSD-4.x: rewritten the ports of stackable templates for FreeBSD 4.x.
  Verified on 4.[5678].  Tested with base0fs, wrapfs, and cryptfs using a
  large compile build, fsx, and our own home-brewed tools.

- Linux-2.4 templates:
	* stacking on extended attribute methods
	* MAJOR OVERHAUL AND FIXES of SCA CODE (gzipfs, uuencodefs, copyfs)

Minor new features and changes:

- Remove duplicate template directories from source tree.  Change fistgen so
  it first looks for an OS-specific template directory and then a more
  general directory.  For example, if uname is "FreeBSD-4.8-RELEASE", then
(Continue reading)

Permalink | Reply | 0 comments |
headers
Yar Tikhiy | 4 Aug 2003 13:58
Picon
Favicon

FFS addressing unit

Hi there,

While poring over <ufs/ffs/fs.h> in order to better understand the
internals of FFS, I noticed that there is a number of comments in
the file refering to a certain "filesystem address."  There is also
a macro named fsbtodb() for turning "filesystem block numbers into
disk block addresses," according to its description.  However, it
seems to be the fragment size that actually serves as the filesystem
addressing unit in all the relevant super-block fields, including
fs_fsbtodb.  Is my conclusion correct?  If so, I'd rather clarify
those comments, so new developers won't confuse fragments with
blocks when doing RTFS.

--

-- 
Yar
_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"
Permalink | Reply | 1 comment |
headers
Forrest Aldrich | 5 Aug 2003 00:53

High Performance Filesystems on FreeBSD-4.x and 5.x

I'm looking for inforamtion about any high-performance filesystems 
available for FreeBSD; namely, the likes of XFS, JFS, Veritas (none there 
that I know of, only for Linux), etc.   If there is a FAQ I've missed, 
kindly point me in the right direction.

Thanks.

_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"
Permalink | Reply | 1 comment |
headers
Brian Bergstrand | 5 Aug 2003 05:17

[OT] NTFS run list help


Hi,

I'm trying to port the NTFS driver to Mac OS X. The PPC chip is big
endian, so I have to worry about byte swapping. I've pretty much got
everything going, except reading files that are not contained in the
MFT. I think that I need to do some byte swapping in ntfs_runtovrun(),
but I would like some help figuring out what is going on in that
routine. Since the buffer is accessed as a byte array, where to byte
swap isn't obvious.

I know this is off topic, but if one of the NTFS developers could point
me in the right direction, I'd really appreciate it.

Thanks.

Brian Bergstrand <http://www.classicalguitar.net/brian/>
PGP Key: <http://www.classicalguitar.net/brian/misc/public_key.txt>
The day Microsoft makes something that doesn't suck is the day they 
start making vacuum cleaners.
Permalink | Reply | 1 comment |
headers
Chris Dillon | 5 Aug 2003 19:14
Picon
Favicon

Re: High Performance Filesystems on FreeBSD-4.x and 5.x

On Mon, 4 Aug 2003, Forrest Aldrich wrote:

> I'm looking for inforamtion about any high-performance filesystems
> available for FreeBSD; namely, the likes of XFS, JFS, Veritas (none
> there that I know of, only for Linux), etc.  If there is a FAQ I've
> missed, kindly point me in the right direction.

FreeBSD's high-performance filesystem is called "FFS", which is used
by default.  There is nothing slow about it except for boot-time
filesystem checking on extremely large (hundreds of gigabytes or more)
filesystems after an un-clean reboot, which could take a while.  It
even has "peace of mind" (reliablility features) like some or all of
the filesystems you listed do.

--

-- 
 Chris Dillon - cdillon(at)wolves.k12.mo.us
 FreeBSD: The fastest and most stable server OS on the planet
 - Available for IA32, IA64, PC98, Alpha, and UltraSPARC architectures
 - x86-64, PowerPC, ARM, MIPS, and S/390 under development
 - http://www.freebsd.org

No trees were harmed in the composition of this message, although some
electrons were mildly inconvenienced.

_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mark Day | 5 Aug 2003 20:34
Picon
Favicon

Re: [OT] NTFS run list help

On Monday, August 4, 2003, at 8:17 PM, Brian Bergstrand wrote:

> I'm trying to port the NTFS driver to Mac OS X.

You might want to look at the Panther developer preview release.  It 
already has a port of the FreeBSD NTFS implementation (though forced to 
be read-only).

-Mark

_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
Yar Tikhiy | 6 Aug 2003 14:28
Picon
Favicon

Re: FFS addressing unit

On Mon, Aug 04, 2003 at 03:58:18PM +0400, Yar Tikhiy wrote:
> 
> While poring over <ufs/ffs/fs.h> in order to better understand the
> internals of FFS, I noticed that there is a number of comments in
> the file refering to a certain "filesystem address."  There is also
> a macro named fsbtodb() for turning "filesystem block numbers into
> disk block addresses," according to its description.  However, it
> seems to be the fragment size that actually serves as the filesystem
> addressing unit in all the relevant super-block fields, including
> fs_fsbtodb.  Is my conclusion correct?  If so, I'd rather clarify
> those comments, so new developers won't confuse fragments with
> blocks when doing RTFS.

For interested parties:  I've been told in a private reply that it
was indeed a fragment that was a primary addressing unit in FFS.

--

-- 
Yar
_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
Craig Carey | 12 Aug 2003 23:48
Picon
Favicon

"security" prevents destruction of hard disks


The sysinstall installer is able to delete most of a hard disk.

http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/29375 [1 Aug 2001]
    "the disk editor used by /stand/sysinstall gets confused by
     slices that are not labelled in order and writes the
     partition table incorrectly."

http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/47384 [22 Jan 2003]
   "Machine has two disks, ad0 (existing 5.0 system) and da0 (scratch
   disk).  Selecting da0 as the target for 'partition' and then
   following that by the sequence 'label/distribution/commit'
   results in a wiped ad0."

For bug i386/29375 [disordered primary partitions], the bug is
outside of the "sysinstall" directory.

The i386/29375 bug report does not mention data loss but I guess
that is the bug that got a big fraction of one of my hard disks
a few years ago.

Now reasonably priced IDE hard disk is about 160GB in size. FreeBSD
can delete the data on that.

The OECD 1980 principles of the 'Guidelines on the Protection of Privacy
and Transborder Flows of Personal Data' (Paris, 1980) rule out the
loss of personal information in computers.

Here is that principle quoted:
>---------------------------------------------------------------------------
(Continue reading)

Permalink | Reply | 501 comments |
headers
Kris Kennaway | 13 Aug 2003 05:43

Re: "security" prevents destruction of hard disks

On Wed, Aug 13, 2003 at 09:48:12AM +1200, Craig Carey wrote:
> 
> 
> The sysinstall installer is able to delete most of a hard disk.

THE BLACK HELICOPTERS ARE HOVERING OUTSIDE YOUR WINDOWS!!!

Kris
Permalink | Reply | 501 comments |

Gmane