October 19, 200817 yr I just installed a new parity drive(1.5 TB) to replace my old 1 TB drive. i plugged it in turned the machine back on, and in the command area it says Stopped, upgrading parity. first of all, this is normal right? i would assume it has to format the drive and everything, but i didn't start the array or anything. It just did it on its own upon booting up. Second of all should i push the start botton now, or does it have to go thru a process first? I cant tell because there is now indication it is actually doing anything other than saying upgrading parity. My third question is about how long does it generally take for a 1.5 TB drive to do its thing and be ready to go? I'm in know rush, i was just wondering. thank you
October 20, 200817 yr I just installed a new parity drive(1.5 TB) to replace my old 1 TB drive. i plugged it in turned the machine back on, and in the command area it says Stopped, upgrading parity. first of all, this is normal right? i would assume it has to format the drive and everything, but i didn't start the array or anything. It just did it on its own upon booting up. Second of all should i push the start botton now, or does it have to go thru a process first? I cant tell because there is now indication it is actually doing anything other than saying upgrading parity. My third question is about how long does it generally take for a 1.5 TB drive to do its thing and be ready to go? I'm in know rush, i was just wondering. thank you It is not yet doing anything, that message is misleading... It means "You are in the process of upgrading parity, not that it is" You now need to press "Start" to get it going. While it is in progress, you may press the "Refresh" button to see its progress as it will show the estimated time to completion and the percentage completed so far. The initial estimates are wildly incorrect, as they don't take into consideration the spin-up time of the drives. Once you get a few percent in, it will give a better estimate. Also, the estimate is based on equal sized drives. As the smaller drives are completely read in a mixed size array, the parity check progress will speed up. The final 250 Gig on my parity calc process only needs to write to the parity disk, and not read any data disks, as they are all smaller, therefore it goes really fast. The time it takes to compute parity depends on the number of disks in your array and the sizes of the disks. The process must read every block of data, used or not, on every data drive, and write every block of data on the parity drive with the computed parity. I have a 1T parity drive, and all my data drives drives are 750 Gig or smaller, smallest is 250 Gig. A full parity check takes about 14 hours on my older IDE disk based array with 12 data drives. A more modern array with SATA drives can do it in 5 or 6 hours. A 1.5T array will take longer of course. Joe L.
October 20, 200817 yr Author Thank you so much. I would have been here for three days pushing refresh waiting for it to be done. i appreciate it
May 21, 200917 yr Continueing on the theme of this thread topic... About how long should it take for a reiserfsk check of a drive to complete? In my case I'm running the check on a 1TB drive.
May 21, 200917 yr The reiserfsck tool is for checking file systems, so the time it takes is not directly related to the physical size of the drive. It is related to how many files are stored, and and how much disk storage space they are using. I've never seen it take very long for the standard checking option, maybe 5 minutes or so, but then my directory tree has never been that large. Just a guess here, for a ballpark figure, but depending on whether your 1TB drive is empty or full, it could take between a few seconds to perhaps 15 minutes. Someone else can probably give you a more accurate figure. Edit: the --rebuild-tree and the other similar option will of course take a LOT longer!
May 21, 200917 yr I ran reiserfsck recently on one of my 1T drives. I also had no idea how long to expect it to run. I'd say it took 1/2 hour, maybe a bit longer. This is from memory, maybe it just felt like that long.
May 21, 200917 yr Well, disc1 took 1 hour 20 minutes. Here's the output: ########### reiserfsck --check started at Thu May 21 06:42:01 2009 ########### Replaying journal.. Reiserfs journal '/dev/md1' in blocks [18..8211]: 0 transactions replayed finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 237947 Internal nodes 1560 Directories 10807 Other files 140372 Data block pointers 222490350 (801395 of them are zero) Safe links 0 ########### reiserfsck finished at Thu May 21 08:02:39 2009 ###########
Archived
This topic is now archived and is closed to further replies.