On 11/21/2010 2:16 PM, Adam Vande More wrote:
On Sun, Nov 21, 2010 at 10:56 AM, Tim Daneliuk tun...@tundraware.com
mailto:tun...@tundraware.com wrote:
This drive is being used as a backup drive for all the workstations on
this particular network, and reliable is much more
The other day I mentioned I had a problem with a Samba-shared drive that
was just installed blowing up. When I rebuilt it, I forgot to enable
softupdates but the drive seems to be working flawlessly. I understand
it is possible to do this after-the-fact with tunefs. Some questions:
Do I
On Sun, Nov 21, 2010 at 10:56 AM, Tim Daneliuk tun...@tundraware.comwrote:
This drive is being used as a backup drive for all the workstations on
this particular network, and reliable is much more important than
slightly faster.
As someone already said, SU is probably not the culprit here.
Tim Daneliuk wrote:
The other day I mentioned I had a problem with a Samba-shared drive that
was just installed blowing up. When I rebuilt it, I forgot to enable
softupdates but the drive seems to be working flawlessly. I understand
it is possible to do this after-the-fact with tunefs.
On Sun, Nov 21, 2010 at 2:16 PM, Adam Vande More amvandem...@gmail.comwrote:
Although from what you describe my choice for the drive would be gjournal +
UFS. If you've got a lot of asynchronous IO that's a better solution.
Instead of asynchronous, I meant multi-threaded. gjournal + UFS
