Large file system creation
Hi all. I'm trying to create a ~9TB partition on a new file server. I thought FreeBSD now supported this (I'm on 7.0), but I can't figure it out. I go into sysinstall, create the partition in fdisk using A = Use Entire Disk), write it to disk, exit sysinstall and re-run it...and sysinstall doesn't show what it showed before I exited last time. Can someone shed some light on what I'm doing wrong here? Thanks, --Brian -- _-=-_-=-_-=-_-=-_-=-_-=-_-=-_-=-_-=-_-=-_-=-_ Brian McCann I don't have to take this abuse from you -- I've got hundreds of people waiting to abuse me. -- Bill Murray, Ghostbusters ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large file system creation
On Tue, Apr 08, 2008 at 08:39:48AM -0400, Brian McCann wrote: Hi all. I'm trying to create a ~9TB partition on a new file server. I thought FreeBSD now supported this (I'm on 7.0), but I can't figure it out. I go into sysinstall, create the partition in fdisk using A = Use Entire Disk), write it to disk, exit sysinstall and re-run it...and sysinstall doesn't show what it showed before I exited last time. Can someone shed some light on what I'm doing wrong here? The filesystem (UFS2) supports disks larger than 2TB, but fdisk(8) and bsdlabel(8) (which are what sysinstall uses to partition the disk) do not support disks larger than 2TB due to limitations in the on-disk format they use. You will need to use gpt(8) instead to partition your disk. This cannot be done from sysinstall and you normally cannot boot from a gpt(8)-partitioned disk due to lack of support in the BIOS of most PC. -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large file system creation
Hi all. I'm trying to create a ~9TB partition on a new file server. I thought FreeBSD now supported this (I'm on 7.0), but I can't figure it out. I go into sysinstall, create the partition in fdisk using A = Use Entire Disk), write it to disk, exit sysinstall and re-run it...and sysinstall doesn't show what it showed before I exited last time. Can someone shed some light on what I'm doing wrong here? The filesystem (UFS2) supports disks larger than 2TB, but fdisk(8) and bsdlabel(8) (which are what sysinstall uses to partition the disk) do not support disks larger than 2TB due to limitations in the on-disk format they use. You will need to use gpt(8) instead to partition your disk. or don't partition at all This cannot be done from sysinstall and you normally cannot boot from a gpt(8)-partitioned disk due to lack of support in the BIOS of most PC. or use old disk, pendrive, DVD-ROM etc. for booting ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large file system creation
That looks like what I need. I've got a seperate 32GB array to boot off of, so that's perfect. Now to just read some man pages. Thanks! --Brian On Tue, Apr 8, 2008 at 9:30 AM, Erik Trulsson [EMAIL PROTECTED] wrote: On Tue, Apr 08, 2008 at 08:39:48AM -0400, Brian McCann wrote: Hi all. I'm trying to create a ~9TB partition on a new file server. I thought FreeBSD now supported this (I'm on 7.0), but I can't figure it out. I go into sysinstall, create the partition in fdisk using A = Use Entire Disk), write it to disk, exit sysinstall and re-run it...and sysinstall doesn't show what it showed before I exited last time. Can someone shed some light on what I'm doing wrong here? The filesystem (UFS2) supports disks larger than 2TB, but fdisk(8) and bsdlabel(8) (which are what sysinstall uses to partition the disk) do not support disks larger than 2TB due to limitations in the on-disk format they use. You will need to use gpt(8) instead to partition your disk. This cannot be done from sysinstall and you normally cannot boot from a gpt(8)-partitioned disk due to lack of support in the BIOS of most PC. -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] -- _-=-_-=-_-=-_-=-_-=-_-=-_-=-_-=-_-=-_-=-_-=-_ Brian McCann I don't have to take this abuse from you -- I've got hundreds of people waiting to abuse me. -- Bill Murray, Ghostbusters ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large file system creation
Hmm...didn't think of that...didn't think fsck used that much RAM...and thought it was independent of the file system size. Right now it's got 2GB. On Tue, Apr 8, 2008 at 11:28 AM, Alexandre Biancalana [EMAIL PROTECTED] wrote: On 4/8/08, Brian McCann [EMAIL PROTECTED] wrote: That looks like what I need. I've got a seperate 32GB array to boot off of, so that's perfect. Now to just read some man pages. Thanks! How many memory do you have in this machine ?? To fsck 9 TB you will need a LOT of memory -- _-=-_-=-_-=-_-=-_-=-_-=-_-=-_-=-_-=-_-=-_-=-_ Brian McCann I don't have to take this abuse from you -- I've got hundreds of people waiting to abuse me. -- Bill Murray, Ghostbusters ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large file system creation
On 4/8/08, Brian McCann [EMAIL PROTECTED] wrote: That looks like what I need. I've got a seperate 32GB array to boot off of, so that's perfect. Now to just read some man pages. Thanks! How many memory do you have in this machine ?? To fsck 9 TB you will need a LOT of memory ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large file system creation
That looks like what I need. I've got a seperate 32GB array to boot off of, so that's perfect. Now to just read some man pages. Thanks! How many memory do you have in this machine ?? To fsck 9 TB you will there is swap too . but my 1.4TB partition can be fsck'ed on 1GB RAM without swap. need a LOT of memory depends of block sized and inode counts. it will be most likely large 32K blocks, so quick fsck and little RAM ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large file system creation
On 4/8/08, Brian McCann [EMAIL PROTECTED] wrote: Hmm...didn't think of that...didn't think fsck used that much RAM...and thought it was independent of the file system size. Right now it's got 2GB. so better you think a little more before execute and do some tests before production too... Try gjournal ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large file system creation
On Tuesday 08 April 2008 11:20:58 am Wojciech Puchar wrote: That looks like what I need. I've got a seperate 32GB array to boot off of, so that's perfect. Now to just read some man pages. Thanks! How many memory do you have in this machine ?? To fsck 9 TB you will there is swap too . but my 1.4TB partition can be fsck'ed on 1GB RAM without swap. need a LOT of memory depends of block sized and inode counts. it will be most likely large 32K blocks, so quick fsck and little RAM In my experience with UFS2 and fsck you will want to have a gig of ram per TB of filesystem. You can get by with less sometimes, eventually you'll get bit. Most mere mortals don't take UFS2 past 6-8TB in production. There are of course exceptions -- Thanks, Josh Paetzel PGP: 8A48 EF36 5E9F 4EDA 5A8C 11B4 26F9 01F1 27AF AECB signature.asc Description: This is a digitally signed message part.
Re: Large file system creation
it will be most likely large 32K blocks, so quick fsck and little RAM In my experience with UFS2 and fsck you will want to have a gig of ram per TB of filesystem. You can get by with less sometimes, eventually you'll get bit. Most mere mortals don't take UFS2 past 6-8TB in production. There are of course exceptions you talk about VM, not real memory. i don't think making 10GB swap is a problem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large file system creation
On 4/8/08, Wojciech Puchar [EMAIL PROTECTED] wrote: it will be most likely large 32K blocks, so quick fsck and little RAM In my experience with UFS2 and fsck you will want to have a gig of ram per TB of filesystem. You can get by with less sometimes, eventually you'll get bit. Most mere mortals don't take UFS2 past 6-8TB in production. There are of course exceptions you talk about VM, not real memory. i don't think making 10GB swap is a problem. The problem is the time that it will take to fsck a 9TB filesystem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large file system creation
you talk about VM, not real memory. i don't think making 10GB swap is a problem. The problem is the time that it will take to fsck a 9TB filesystem. depends mostly of file count not size. my 1.4TB partition is checked shorter than 20GB squid partition ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large file system creation
On Tue, Apr 8, 2008 at 9:38 AM, Wojciech Puchar [EMAIL PROTECTED] wrote: Hi all. I'm trying to create a ~9TB partition on a new file server. I thought FreeBSD now supported this (I'm on 7.0), but I can't figure it out. I go into sysinstall, create the partition in fdisk using A = Use Entire Disk), write it to disk, exit sysinstall and re-run it...and sysinstall doesn't show what it showed before I exited last time. Can someone shed some light on what I'm doing wrong here? The filesystem (UFS2) supports disks larger than 2TB, but fdisk(8) and bsdlabel(8) (which are what sysinstall uses to partition the disk) do not support disks larger than 2TB due to limitations in the on-disk format they use. You will need to use gpt(8) instead to partition your disk. or don't partition at all This cannot be done from sysinstall and you normally cannot boot from a gpt(8)-partitioned disk due to lack of support in the BIOS of most PC. or use old disk, pendrive, DVD-ROM etc. for booting ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Seems like a shame to boot a nice 9TB disk pack off a floppy Disk or a Pen drive. I mean you do what you have to but that just screams 'workaround' ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large file system creation
On Tuesday 08 April 2008 21:12:00 Edward Capriolo wrote: Seems like a shame to boot a nice 9TB disk pack off a floppy Disk or a Pen drive. I mean you do what you have to but that just screams 'workaround' Or worrying about 1 minute longer boot cycle on 90 days+ uptime screams optimization fever. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large file system creation
On our older servers that wouldn't even recognize a 2TB partition (which is where the OS was too), we used a CF card and CF card adapter to boot from. Slightly more gracious... CD/DVD drive isn't bad too. anyway - you don't change kernel every day. or pendrive. possibly floppy but i don't know if kernel (with at least disk driver and ufs) can fit on it compressed. i don't think so. ZIPdrives internal (i've got a bit for free). netboot or simply small hard disk. there are lot of options. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large file system creation
Seems like a shame to boot a nice 9TB disk pack off a floppy Disk or a Pen drive. I mean you do what you have to but that just screams 'workaround' Or worrying about 1 minute longer boot cycle on 90 days+ uptime screams doesn't matter at all. it is workaround, but over strange BIOS software, not FreeBSD ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large file system creation
On our older servers that wouldn't even recognize a 2TB partition (which is where the OS was too), we used a CF card and CF card adapter to boot from. Slightly more gracious... On Tue, Apr 8, 2008 at 3:12 PM, Edward Capriolo [EMAIL PROTECTED] wrote: On Tue, Apr 8, 2008 at 9:38 AM, Wojciech Puchar [EMAIL PROTECTED] wrote: Hi all. I'm trying to create a ~9TB partition on a new file server. I thought FreeBSD now supported this (I'm on 7.0), but I can't figure it out. I go into sysinstall, create the partition in fdisk using A = Use Entire Disk), write it to disk, exit sysinstall and re-run it...and sysinstall doesn't show what it showed before I exited last time. Can someone shed some light on what I'm doing wrong here? The filesystem (UFS2) supports disks larger than 2TB, but fdisk(8) and bsdlabel(8) (which are what sysinstall uses to partition the disk) do not support disks larger than 2TB due to limitations in the on-disk format they use. You will need to use gpt(8) instead to partition your disk. or don't partition at all This cannot be done from sysinstall and you normally cannot boot from a gpt(8)-partitioned disk due to lack of support in the BIOS of most PC. or use old disk, pendrive, DVD-ROM etc. for booting ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Seems like a shame to boot a nice 9TB disk pack off a floppy Disk or a Pen drive. I mean you do what you have to but that just screams 'workaround' -- _-=-_-=-_-=-_-=-_-=-_-=-_-=-_-=-_-=-_-=-_-=-_ Brian McCann I don't have to take this abuse from you -- I've got hundreds of people waiting to abuse me. -- Bill Murray, Ghostbusters ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large File System?
Hmm I wonder what the advantages of this over softupdates are. Never really saw the need for the google summer of code project etc for this when we have softupdates But I guess I must be missing something -- martin On 8/9/06, Matthew Seaman [EMAIL PROTECTED] wrote: Nikolas Britton wrote: You've never had to fsck a 2TB+ array, have you?... This is why we DEMAND journaling UFS2. or ZFS. Ask and ye shall receive. http://lists.freebsd.org/pipermail/freebsd-current/2006-August/064932.html Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large File System?
The advantage is never having to run fsck again... on large filesystems this takes a long long long time. 16 hours would not be unheard of. On 8/10/06, Martin Hepworth [EMAIL PROTECTED] wrote: Hmm I wonder what the advantages of this over softupdates are. Never really saw the need for the google summer of code project etc for this when we have softupdates But I guess I must be missing something -- martin On 8/9/06, Matthew Seaman [EMAIL PROTECTED] wrote: Nikolas Britton wrote: You've never had to fsck a 2TB+ array, have you?... This is why we DEMAND journaling UFS2. or ZFS. Ask and ye shall receive. http://lists.freebsd.org/pipermail/freebsd-current/2006-August/064932.html Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large File System?
On 08/08/06, Martin Hepworth [EMAIL PROTECTED] wrote: Softupdates are the FreeBSD equivalent. From my point of view they perform better than a traditional journaling FS (do a google search for the original usenix papers on these). Journalling means not having to fsck the file system in the event of an unclean shutdown. So it's wrong to describe softupdates as equivalent. It's not. I also find they speed up I/O quite alot, esp for fast changing filesystems like mail spools. Certainly I have found using softupdates to be considerably faster than without. martin Frem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large File System?
On 08/08/06, Chad Leigh -- Shire.Net LLC [EMAIL PROTECTED] wrote: Right now, if no fsck is really really important to you for your data store, then get an OpenSolaris system and put ZFS on it. Never fsck again as it is ALWAYS (they claim) in a coherent state. Or wait for ZFS to show up on FreeBSD Indeed. However as most of my platform is running FreeBSD the problem doesn't go away. Not just for the above reasons, I am implementing a Solaris server with 1.7TB on ZFS and sharing it to a bunch of FreeBSD machines over nfs on dedicated gigabit with jumbo frames on separate interfaces from the standard default interface. (My main reason was to not have storage tied to an individual worker server) I would have used Solaris for this a while ago, but there were no drivers for the RAID card :-( Hence, Linux Chad Frem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large File System?
On 8/8/06, Martin Hepworth [EMAIL PROTECTED] wrote: On 8/8/06, Freminlins [EMAIL PROTECTED] wrote: snip The single most important thing missing for me in FreeBSD is a journalling file system as I would use it on every box. snip Softupdates are the FreeBSD equivalent. From my point of view they perform better than a traditional journaling FS (do a google search for the original usenix papers on these). I also find they speed up I/O quite alot, esp for fast changing filesystems like mail spools. You've never had to fsck a 2TB+ array, have you?... This is why we DEMAND journaling UFS2. or ZFS. -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large File System?
Nikolas Britton wrote: You've never had to fsck a 2TB+ array, have you?... This is why we DEMAND journaling UFS2. or ZFS. Ask and ye shall receive. http://lists.freebsd.org/pipermail/freebsd-current/2006-August/064932.html Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Large File System?
On 08/08/06, Atom Powers [EMAIL PROTECTED] wrote: Thanks. I found my problem. (Sysinstall, aka fdisk, won't do more that 1.2TB.) BTW, anybody have any good advice on how to manage a large file system? Unfortunately I have to say consider Solaris or Linux as they have journalling file systems. Although I have a couple of big file systems on FreeBSD, it is not a pretty sight if there is some sort of problem. Recently our colo lost power. The two boxes that needed manually fixing were the two big file system boxes. Background fsck did not fix them. To compare, we have one almost identical box running Linux. It came straight back up courtesy of ext3. Ignoring all the suggestions to get UPS (the colo had generator backed UPS which failed), etc, problems can/do happen. And when they do, journalling for big file systems is very useful. The single most important thing missing for me in FreeBSD is a journalling file system as I would use it on every box. You don't need to do anything more to manage big file systems per se. How big a file system are you going to create? What are you going to use it for? That might help with suggestions. --Atom Powers-- Frem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large File System?
Well ext3 can have problems too - I've had numerous problems with that, and had to revert back to ext2 to get the filesystem to mount. XFS is much better. And I've had no problems with UFS/softupdates on FreeBSD, but YMMV as they say. But yes, when ZFS gets ported to FreeBSD we will all very happy. -- Martin On 8/8/06, Freminlins [EMAIL PROTECTED] wrote: On 08/08/06, Atom Powers [EMAIL PROTECTED] wrote: Thanks. I found my problem. (Sysinstall, aka fdisk, won't do more that 1.2TB.) BTW, anybody have any good advice on how to manage a large file system? Unfortunately I have to say consider Solaris or Linux as they have journalling file systems. Although I have a couple of big file systems on FreeBSD, it is not a pretty sight if there is some sort of problem. Recently our colo lost power. The two boxes that needed manually fixing were the two big file system boxes. Background fsck did not fix them. To compare, we have one almost identical box running Linux. It came straight back up courtesy of ext3. Ignoring all the suggestions to get UPS (the colo had generator backed UPS which failed), etc, problems can/do happen. And when they do, journalling for big file systems is very useful. The single most important thing missing for me in FreeBSD is a journalling file system as I would use it on every box. You don't need to do anything more to manage big file systems per se. How big a file system are you going to create? What are you going to use it for? That might help with suggestions. --Atom Powers-- Frem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large File System?
On 8/8/06, Freminlins [EMAIL PROTECTED] wrote: On 08/08/06, Atom Powers [EMAIL PROTECTED] wrote: Thanks. I found my problem. (Sysinstall, aka fdisk, won't do more that 1.2TB.) BTW, anybody have any good advice on how to manage a large file system? ... The single most important thing missing for me in FreeBSD is a journalling file system as I would use it on every box. What exactly does a journaling file system give you? As I understand it, it doesn't prevent corruption and it doesn't help you fix the corruption when it occurs. You don't need to do anything more to manage big file systems per se. How big a file system are you going to create? What are you going to use it for? That might help with suggestions. File server. It's a Promise VTrak M300p, SCSI attached storage. Frankly I'm more worried about the system crashing than the storage device ( UPS, battery pack for the RAID controller, redundant power supplies ). 2.5TB file system, used mostly for archival storage. Of the initial 2.0TB of data, I expect only about 2-3% to change on a weekly basis. I have another 1.5TB Fiber Channel cabinet that I plan on using to store roaming profiles ( for MS Win uers) and home drives (for *nix users). -- -- Perfection is just a word I use occasionally with mustard. --Atom Powers-- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large File System?
In the last episode (Aug 08), Atom Powers said: On 8/8/06, Freminlins [EMAIL PROTECTED] wrote: On 08/08/06, Atom Powers [EMAIL PROTECTED] wrote: Thanks. I found my problem. (Sysinstall, aka fdisk, won't do more that 1.2TB.) BTW, anybody have any good advice on how to manage a large file system? ... The single most important thing missing for me in FreeBSD is a journalling file system as I would use it on every box. What exactly does a journaling file system give you? As I understand it, it doesn't prevent corruption and it doesn't help you fix the corruption when it occurs. Journalling lets you roll back/forward a partially-commited filesystem change, so a full filesytem check isn't required to mark it clean after an unintended system reset. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large File System?
On 8/8/06, Freminlins [EMAIL PROTECTED] wrote: snip The single most important thing missing for me in FreeBSD is a journalling file system as I would use it on every box. snip Softupdates are the FreeBSD equivalent. From my point of view they perform better than a traditional journaling FS (do a google search for the original usenix papers on these). I also find they speed up I/O quite alot, esp for fast changing filesystems like mail spools. -- martin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large File System?
On 08/08/06, Atom Powers [EMAIL PROTECTED] wrote: What exactly does a journaling file system give you? As I understand it, it doesn't prevent corruption and it doesn't help you fix the corruption when it occurs. As answered by Dan Nelson. It saves time (sometimes a lot) in the event of an unclean shutdown/ File server. It's a Promise VTrak M300p, SCSI attached storage. Frankly I'm more worried about the system crashing than the storage device ( UPS, battery pack for the RAID controller, redundant power supplies ). Yes, I had all that. It is of absolutely no use in the event of an unclean shutdown (on FreeBSD). If the file system itself is dirty, it will need to fsckd. The bigger the file system, the longer it takes (generall). That is what journalling saves you. To give you some indication of what this means in real life, I'll refer (again, sorry) to a power outage we suffered in our colo. This is FreeBSD on modern hardware: Jul 23 17:52:05 weeble kernel: WARNING: /var was not properly dismounted Jul 23 17:55:52 weeble fsck: /dev/aacd0s1f: 1352 files, 956469 used, 13988364 free (1484 frags, 1748360 blocks, 0.0% fragmentation) I've snipped out the logs in between. But that's nearly 4 minutes to get itself sorted out. That file system has only 1.9GB of data. Our Solaris boxes came up straight away. 2.5TB file system, used mostly for archival storage. Of the initial 2.0TB of data, I expect only about 2-3% to change on a weekly basis. I have another 1.5TB Fiber Channel cabinet that I plan on using to store roaming profiles ( for MS Win uers) and home drives (for *nix users). Depending on the size of the files, you may wish to use a different block size. Also I've found that on large file systems you may wish to change is the minfree setting. You can do this either when running newfs, or tunefs. The default setting is 8%. On 2.5TB file systems that's a lot. If you don't know what this means check out the man pages. That is about the only management you will need to do. Perfection is just a word I use occasionally with mustard. --Atom Powers-- Frem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large File System?
On Aug 8, 2006, at 1:01 PM, Freminlins wrote: Yes, I had all that. It is of absolutely no use in the event of an unclean shutdown (on FreeBSD). If the file system itself is dirty, it will need to fsckd. The bigger the file system, the longer it takes (generall). That is what journalling saves you. To give you some indication of what this means in real life, I'll refer (again, sorry) to a power outage we suffered in our colo. This is FreeBSD on modern hardware: Jul 23 17:52:05 weeble kernel: WARNING: /var was not properly dismounted Jul 23 17:55:52 weeble fsck: /dev/aacd0s1f: 1352 files, 956469 used, 13988364 free (1484 frags, 1748360 blocks, 0.0% fragmentation) I've snipped out the logs in between. But that's nearly 4 minutes to get itself sorted out. That file system has only 1.9GB of data. Our Solaris boxes came up straight away. Right now, if no fsck is really really important to you for your data store, then get an OpenSolaris system and put ZFS on it. Never fsck again as it is ALWAYS (they claim) in a coherent state. Or wait for ZFS to show up on FreeBSD Not just for the above reasons, I am implementing a Solaris server with 1.7TB on ZFS and sharing it to a bunch of FreeBSD machines over nfs on dedicated gigabit with jumbo frames on separate interfaces from the standard default interface. (My main reason was to not have storage tied to an individual worker server) Chad --- Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider chad at shire.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Large File System?
Somebody please tell me it is possible to create a file system larger than 1.2TB. -- -- Perfection is just a word I use occasionally with mustard. --Atom Powers-- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large File System?
Atom Powers [EMAIL PROTECTED] writes: Somebody please tell me it is possible to create a file system larger than 1.2TB. It is: FilesystemSizeUsed Avail Capacity Mounted on /dev/concat/c01.6T846G648G57%/backup -- Christian Laursen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Large File System?
On 8/7/06, Christian Laursen [EMAIL PROTECTED] wrote: Atom Powers [EMAIL PROTECTED] writes: Somebody please tell me it is possible to create a file system larger than 1.2TB. It is: FilesystemSizeUsed Avail Capacity Mounted on /dev/concat/c01.6T846G648G57%/backup Thanks. I found my problem. (Sysinstall, aka fdisk, won't do more that 1.2TB.) BTW, anybody have any good advice on how to manage a large file system? -- -- Perfection is just a word I use occasionally with mustard. --Atom Powers-- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
