I want to write a start up script to take an mapped drive, change the drive letter, then put a different share on the original drive. How can this be done?
I understand what LVM is and what it accomplishes, but I feel like I am missing some things.
Lets say we have two physical drives, sda and sdb. Both are 100 Megs. I put them into VolumeGroup1 and create one 200 meg LogicalVolume1.
What would happen if I create a 150 meg file? Would 100 megs physically be on sda and 50 on sdb? If so, what tells the OS that a piece of the file is on one drive, and another piece is on the other?
What about drive failure? Assuming no RAID, if sdb fails, will all the data on sda be lost? Is there anyway to control what files are on what physical drives?
How do you generally manage LVM? Do you create one or two large Volume Groups then make partitions as it makes sense? Any other tips?
I just came across RAIN, Redundant Array of Independent Network interfaces, aka Channel Bonding for the first time.
Is this a technology which is worth implementing? Any pitfalls? Or would one be better off upgrading to fiber?
Cheap NICs like Realtek utilize the CPU to do some work. Better NICs like the Intel Pro line perform more work on the NIC leaving the CPU with less to do.
When purchasing NICs, how can you tell if the it will result in lower CPU utilization than a cheap NIC? Of the ones which do reduce CPU utilization, are some better than others?
I am evaluating Fedora 11. I mounted a NFS share from a NAS and I noticed that hsqldb is listed as both the owner and group for the directory I mounted the NFS share to. Why is this?
What are some pitfalls or lessons learned after converting existing hardware to a virtualized environment? Is there anything you tried to virtualize but will never do again?
This is the canonical question for "Should I build coomputing hardware myself?" questions.
I have put together countless PCs, but never a large server. The geek in me says build it, but the realist in me says let the manufacturer handle it when there is a problem. Ignoring the time penalty involved with the initial assembly time of a built one, which is a better solution? Have you ever run into a problem with a home build server that would have been solved easier/quicker/cheaper by going with a manufacturer? Are there any features that manufacturers give that aren't easily attainable with a home built server?
I am considering switching from FreeNAS to OpenFiler. One issue I see with this is that all the hard drives in my NAS are formatted to UFS. I tried but was unable to mount them in Fedora. Is there any way I can extract my data from the UFS hard drive without a FreeBSD OS?
Are there any studies or evidence which show that mounting a hard drive horizontally is better than vertically for the lifespan of the device? Or upside down, or any direction for that matter.
A few years ago I was told to avoid S.M.A.R.T. like the plague. The reasoning was that the stress the testing puts on the drive will actually cause it to fail.
Is this still the case? If not, what is a reasonable frequency to run tests? If I should still be avoiding it, what is a better way to monitor the health of my hard drives?
I set up FreeNAS on an Asus P5B (Basic) with a Pentium D 3ghz processor (may be overkill, but it is a spare machine). The CPU usually runs around 750mhz-1500mhz. I am aiming for a quiet machine so the only fan is on the CPU's Heatsink and the power supply. The hard drives and cpu heatsink remain cool to the touch, but the Northbridge's heatsink and the area around the power supply are very warm to the touch, bordering on hot.
I am not sure if too much can be done for the power supply, but for the North bridge, are there any settings I can change in the BIOS (or even FreeNAS) which will help that run cooler?
I have FreeNAS exposing an NFS. How do I access this from Windows 7? I have enabled the "Services for NFS" within Windows Features.
I just built a new(ish) machine and I stuck 6 gigs of RAM into it. I decided to give the RC of Windows 7 (64bit) a try. As I was using it I noticed the machine said it had 6 gigs of ram, but only 5 was usable. This drove me a little nuts because it was able to detect 6 gigs. And it clearly wasn't this issue "Dude, Where's My 4 Gigabytes of RAM?" because I was getting 5 gigs. I also noticed that the BIOS was only reporting 5 gigs as usable. I thought it might be a bad RAM chip so I started swapping them in and out. Eventually I determined they were all good. I noticed the Memory remapping feature in the BIOS so I gave that a try and Windows and the BIOS is reporting all 6 gigs are usable.
Why does this remapping need to be done? Shouldn't the BIOS automatically be using all of the ram?
I just set up a FreeNAS server with a terabyte drive. I want to only have one hard drive in each machine so I have been taking as much data as possible and sending it over the LAN to FreeNAS. I have noticed at least one file didn't copy properly and is now corrupt. (I am also noticing some strange permission issues, but that is another question.) Now that most of the data is over on the FreeNAS server, is there an automated way of verifying nothing else is corrupt?
I am not exactly sure how to describe how the file was corrupt. Basically it appeared to be a 178 megabyte video file, but when accessing it to play or even move, the windows machine accessing it gave a generic could not access error message. I used FreeNAS's web copy interface to move the file, once it was moved, the file was 76 megs, and could not be played.