Shrinking file system taking a lot of time, is this normal?
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
up vote
15
down vote
favorite
I'm using GParted to shrink the partition on my 500 GB external hard drive to a 220 GB partition. It contains about 210 GB of data.
I'm shrinking it to convert FAT32 to EXT2. It has been almost an hour. My hard disk heats up so I have continuous ventilation to keep it cool.
Is this lengthy time taken by GParted normal? If not, then how do I safely disconnect it? I don't mind losing the data, but the hard disk is really important. Any suggestions? Also, will running the hard disk for such long hours be harmful?
partitioning hard-drive gparted
add a comment |Â
up vote
15
down vote
favorite
I'm using GParted to shrink the partition on my 500 GB external hard drive to a 220 GB partition. It contains about 210 GB of data.
I'm shrinking it to convert FAT32 to EXT2. It has been almost an hour. My hard disk heats up so I have continuous ventilation to keep it cool.
Is this lengthy time taken by GParted normal? If not, then how do I safely disconnect it? I don't mind losing the data, but the hard disk is really important. Any suggestions? Also, will running the hard disk for such long hours be harmful?
partitioning hard-drive gparted
add a comment |Â
up vote
15
down vote
favorite
up vote
15
down vote
favorite
I'm using GParted to shrink the partition on my 500 GB external hard drive to a 220 GB partition. It contains about 210 GB of data.
I'm shrinking it to convert FAT32 to EXT2. It has been almost an hour. My hard disk heats up so I have continuous ventilation to keep it cool.
Is this lengthy time taken by GParted normal? If not, then how do I safely disconnect it? I don't mind losing the data, but the hard disk is really important. Any suggestions? Also, will running the hard disk for such long hours be harmful?
partitioning hard-drive gparted
I'm using GParted to shrink the partition on my 500 GB external hard drive to a 220 GB partition. It contains about 210 GB of data.
I'm shrinking it to convert FAT32 to EXT2. It has been almost an hour. My hard disk heats up so I have continuous ventilation to keep it cool.
Is this lengthy time taken by GParted normal? If not, then how do I safely disconnect it? I don't mind losing the data, but the hard disk is really important. Any suggestions? Also, will running the hard disk for such long hours be harmful?
partitioning hard-drive gparted
edited May 20 at 20:45
![](https://i.stack.imgur.com/8CW8e.png?s=32&g=1)
![](https://i.stack.imgur.com/8CW8e.png?s=32&g=1)
Zanna
47.8k13117227
47.8k13117227
asked Aug 19 '12 at 20:51
Schweinsteiger
4,57941423
4,57941423
add a comment |Â
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
20
down vote
accepted
It's quite normal for dynamic resizing operations--and particularly shrinking--to take a long time. Files are spread across much, and perhaps most, of the original partition. They have to be re-pieced together to fit them in a smaller space, and the information about where their pieces exist has to be updated. If you are also having the partition automatically converted from FAT32 to ext2, that may take a while as well, as the files are stored somewhat differently.
If it takes more than a day, then I would start thinking there was something wrong.
As for whether or not it's OK to run your hard drive at near its maximum capacity for reads and writes, for hours at a time: yes, this is fine. Your hard drive is, among other things, a mechanical device, so the more it's used, the higher the likelihood of mechanical failure. But all hard drives fail eventually, and there's no reason to expect this one will fail any sooner, just because it runs heavily for hours.
Of course, if it's getting too hot, that is a problem. A properly constructed computer should never allow this to happen, even if the hard drive is reading and writing at 100% capacity for days, weeks, or months without interruption. (Depending on what hard drive you've purchased, running it like this for months might or might not bring about very early failure.) But if you find it is hot, and you're able to cool it with externally applied ventilation, that should be fine.
I don't mind losing the data,but the hard disk is really important.
If you have to cancel the operation, click Cancel. Really anything except cutting power to your computer or to the drive, won't physically damage the drive. Shutting down the operating system, using any method of harshness less than or equal to REISUB, will not be a problem. Even cutting power to the machine is unlikely to cause any real damage, although I would definitely avoid it when possible.
However, you may want to rethink the value you put in a single drive. All hard drives fail eventually, you can't prevent them from failing, and you can't prevent some of them (essentially selected at random) from failing long before you would expect them to fail. Some drives last longer than others (for some uses), and some drives are less likely to fail "early," but hard drives are replaceable (even in laptops) for a reason.
To put it another way: Hard drives' lifetimes are limited, so much so that in any computer where some other component fails first, the computer's craftsmanship should be questioned.
Thank you for that well written comprehensive answer. Oh btw,its an external Hard drive.
â Schweinsteiger
Aug 19 '12 at 21:25
@Schweinsteiger You might expect an external drive (depending on the interface) to be somewhat slower than an internal drive, because each access may take a little longer. As for the drive's lifetime, an external drive is actually an internal drive in an enclosure, so the characteristics and design specifications of the internal drive would be what you'd want to consult, if you wanted to determine how suited the drive is to your needs. (Of course, dynamic partitinon resizing operations probably aren't your usual pattern of use.)
â Eliah Kagan
Aug 19 '12 at 21:29
Oh alright. Thanks again :)
â Schweinsteiger
Aug 19 '12 at 21:34
Does this answer apply no matter what the file system is? I'm in exactly the same situation as OP, but the partition is HFS+. Is there any difference? I mean, isn't FAT32 more fragmented than HFS? Is it normal for HFS+ to take a long time too?
â Revetahw
May 26 '16 at 6:59
add a comment |Â
up vote
1
down vote
Most external drives AFAIK do not have cooling fans, so under the process you described, overheating is expected...and unwanted. There is no need to wear out your hardware before the end of its design lifetime.
I found it quicker and more kind to the hardware, if you copy (not "move") the files to another hard drive temporarily. Or perhaps compress the existing files (7z
, tar
, rar
, or zip
) to one big file, then copy to another drive.
If it's OK to destroy the original files, use GParted (or other disk/partition manager) to immediately reformat the whole drive, defining whatever partitions you want (however many, however big, and whatever filesystems you prefer).
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
20
down vote
accepted
It's quite normal for dynamic resizing operations--and particularly shrinking--to take a long time. Files are spread across much, and perhaps most, of the original partition. They have to be re-pieced together to fit them in a smaller space, and the information about where their pieces exist has to be updated. If you are also having the partition automatically converted from FAT32 to ext2, that may take a while as well, as the files are stored somewhat differently.
If it takes more than a day, then I would start thinking there was something wrong.
As for whether or not it's OK to run your hard drive at near its maximum capacity for reads and writes, for hours at a time: yes, this is fine. Your hard drive is, among other things, a mechanical device, so the more it's used, the higher the likelihood of mechanical failure. But all hard drives fail eventually, and there's no reason to expect this one will fail any sooner, just because it runs heavily for hours.
Of course, if it's getting too hot, that is a problem. A properly constructed computer should never allow this to happen, even if the hard drive is reading and writing at 100% capacity for days, weeks, or months without interruption. (Depending on what hard drive you've purchased, running it like this for months might or might not bring about very early failure.) But if you find it is hot, and you're able to cool it with externally applied ventilation, that should be fine.
I don't mind losing the data,but the hard disk is really important.
If you have to cancel the operation, click Cancel. Really anything except cutting power to your computer or to the drive, won't physically damage the drive. Shutting down the operating system, using any method of harshness less than or equal to REISUB, will not be a problem. Even cutting power to the machine is unlikely to cause any real damage, although I would definitely avoid it when possible.
However, you may want to rethink the value you put in a single drive. All hard drives fail eventually, you can't prevent them from failing, and you can't prevent some of them (essentially selected at random) from failing long before you would expect them to fail. Some drives last longer than others (for some uses), and some drives are less likely to fail "early," but hard drives are replaceable (even in laptops) for a reason.
To put it another way: Hard drives' lifetimes are limited, so much so that in any computer where some other component fails first, the computer's craftsmanship should be questioned.
Thank you for that well written comprehensive answer. Oh btw,its an external Hard drive.
â Schweinsteiger
Aug 19 '12 at 21:25
@Schweinsteiger You might expect an external drive (depending on the interface) to be somewhat slower than an internal drive, because each access may take a little longer. As for the drive's lifetime, an external drive is actually an internal drive in an enclosure, so the characteristics and design specifications of the internal drive would be what you'd want to consult, if you wanted to determine how suited the drive is to your needs. (Of course, dynamic partitinon resizing operations probably aren't your usual pattern of use.)
â Eliah Kagan
Aug 19 '12 at 21:29
Oh alright. Thanks again :)
â Schweinsteiger
Aug 19 '12 at 21:34
Does this answer apply no matter what the file system is? I'm in exactly the same situation as OP, but the partition is HFS+. Is there any difference? I mean, isn't FAT32 more fragmented than HFS? Is it normal for HFS+ to take a long time too?
â Revetahw
May 26 '16 at 6:59
add a comment |Â
up vote
20
down vote
accepted
It's quite normal for dynamic resizing operations--and particularly shrinking--to take a long time. Files are spread across much, and perhaps most, of the original partition. They have to be re-pieced together to fit them in a smaller space, and the information about where their pieces exist has to be updated. If you are also having the partition automatically converted from FAT32 to ext2, that may take a while as well, as the files are stored somewhat differently.
If it takes more than a day, then I would start thinking there was something wrong.
As for whether or not it's OK to run your hard drive at near its maximum capacity for reads and writes, for hours at a time: yes, this is fine. Your hard drive is, among other things, a mechanical device, so the more it's used, the higher the likelihood of mechanical failure. But all hard drives fail eventually, and there's no reason to expect this one will fail any sooner, just because it runs heavily for hours.
Of course, if it's getting too hot, that is a problem. A properly constructed computer should never allow this to happen, even if the hard drive is reading and writing at 100% capacity for days, weeks, or months without interruption. (Depending on what hard drive you've purchased, running it like this for months might or might not bring about very early failure.) But if you find it is hot, and you're able to cool it with externally applied ventilation, that should be fine.
I don't mind losing the data,but the hard disk is really important.
If you have to cancel the operation, click Cancel. Really anything except cutting power to your computer or to the drive, won't physically damage the drive. Shutting down the operating system, using any method of harshness less than or equal to REISUB, will not be a problem. Even cutting power to the machine is unlikely to cause any real damage, although I would definitely avoid it when possible.
However, you may want to rethink the value you put in a single drive. All hard drives fail eventually, you can't prevent them from failing, and you can't prevent some of them (essentially selected at random) from failing long before you would expect them to fail. Some drives last longer than others (for some uses), and some drives are less likely to fail "early," but hard drives are replaceable (even in laptops) for a reason.
To put it another way: Hard drives' lifetimes are limited, so much so that in any computer where some other component fails first, the computer's craftsmanship should be questioned.
Thank you for that well written comprehensive answer. Oh btw,its an external Hard drive.
â Schweinsteiger
Aug 19 '12 at 21:25
@Schweinsteiger You might expect an external drive (depending on the interface) to be somewhat slower than an internal drive, because each access may take a little longer. As for the drive's lifetime, an external drive is actually an internal drive in an enclosure, so the characteristics and design specifications of the internal drive would be what you'd want to consult, if you wanted to determine how suited the drive is to your needs. (Of course, dynamic partitinon resizing operations probably aren't your usual pattern of use.)
â Eliah Kagan
Aug 19 '12 at 21:29
Oh alright. Thanks again :)
â Schweinsteiger
Aug 19 '12 at 21:34
Does this answer apply no matter what the file system is? I'm in exactly the same situation as OP, but the partition is HFS+. Is there any difference? I mean, isn't FAT32 more fragmented than HFS? Is it normal for HFS+ to take a long time too?
â Revetahw
May 26 '16 at 6:59
add a comment |Â
up vote
20
down vote
accepted
up vote
20
down vote
accepted
It's quite normal for dynamic resizing operations--and particularly shrinking--to take a long time. Files are spread across much, and perhaps most, of the original partition. They have to be re-pieced together to fit them in a smaller space, and the information about where their pieces exist has to be updated. If you are also having the partition automatically converted from FAT32 to ext2, that may take a while as well, as the files are stored somewhat differently.
If it takes more than a day, then I would start thinking there was something wrong.
As for whether or not it's OK to run your hard drive at near its maximum capacity for reads and writes, for hours at a time: yes, this is fine. Your hard drive is, among other things, a mechanical device, so the more it's used, the higher the likelihood of mechanical failure. But all hard drives fail eventually, and there's no reason to expect this one will fail any sooner, just because it runs heavily for hours.
Of course, if it's getting too hot, that is a problem. A properly constructed computer should never allow this to happen, even if the hard drive is reading and writing at 100% capacity for days, weeks, or months without interruption. (Depending on what hard drive you've purchased, running it like this for months might or might not bring about very early failure.) But if you find it is hot, and you're able to cool it with externally applied ventilation, that should be fine.
I don't mind losing the data,but the hard disk is really important.
If you have to cancel the operation, click Cancel. Really anything except cutting power to your computer or to the drive, won't physically damage the drive. Shutting down the operating system, using any method of harshness less than or equal to REISUB, will not be a problem. Even cutting power to the machine is unlikely to cause any real damage, although I would definitely avoid it when possible.
However, you may want to rethink the value you put in a single drive. All hard drives fail eventually, you can't prevent them from failing, and you can't prevent some of them (essentially selected at random) from failing long before you would expect them to fail. Some drives last longer than others (for some uses), and some drives are less likely to fail "early," but hard drives are replaceable (even in laptops) for a reason.
To put it another way: Hard drives' lifetimes are limited, so much so that in any computer where some other component fails first, the computer's craftsmanship should be questioned.
It's quite normal for dynamic resizing operations--and particularly shrinking--to take a long time. Files are spread across much, and perhaps most, of the original partition. They have to be re-pieced together to fit them in a smaller space, and the information about where their pieces exist has to be updated. If you are also having the partition automatically converted from FAT32 to ext2, that may take a while as well, as the files are stored somewhat differently.
If it takes more than a day, then I would start thinking there was something wrong.
As for whether or not it's OK to run your hard drive at near its maximum capacity for reads and writes, for hours at a time: yes, this is fine. Your hard drive is, among other things, a mechanical device, so the more it's used, the higher the likelihood of mechanical failure. But all hard drives fail eventually, and there's no reason to expect this one will fail any sooner, just because it runs heavily for hours.
Of course, if it's getting too hot, that is a problem. A properly constructed computer should never allow this to happen, even if the hard drive is reading and writing at 100% capacity for days, weeks, or months without interruption. (Depending on what hard drive you've purchased, running it like this for months might or might not bring about very early failure.) But if you find it is hot, and you're able to cool it with externally applied ventilation, that should be fine.
I don't mind losing the data,but the hard disk is really important.
If you have to cancel the operation, click Cancel. Really anything except cutting power to your computer or to the drive, won't physically damage the drive. Shutting down the operating system, using any method of harshness less than or equal to REISUB, will not be a problem. Even cutting power to the machine is unlikely to cause any real damage, although I would definitely avoid it when possible.
However, you may want to rethink the value you put in a single drive. All hard drives fail eventually, you can't prevent them from failing, and you can't prevent some of them (essentially selected at random) from failing long before you would expect them to fail. Some drives last longer than others (for some uses), and some drives are less likely to fail "early," but hard drives are replaceable (even in laptops) for a reason.
To put it another way: Hard drives' lifetimes are limited, so much so that in any computer where some other component fails first, the computer's craftsmanship should be questioned.
answered Aug 19 '12 at 21:21
Eliah Kagan
79.2k20218359
79.2k20218359
Thank you for that well written comprehensive answer. Oh btw,its an external Hard drive.
â Schweinsteiger
Aug 19 '12 at 21:25
@Schweinsteiger You might expect an external drive (depending on the interface) to be somewhat slower than an internal drive, because each access may take a little longer. As for the drive's lifetime, an external drive is actually an internal drive in an enclosure, so the characteristics and design specifications of the internal drive would be what you'd want to consult, if you wanted to determine how suited the drive is to your needs. (Of course, dynamic partitinon resizing operations probably aren't your usual pattern of use.)
â Eliah Kagan
Aug 19 '12 at 21:29
Oh alright. Thanks again :)
â Schweinsteiger
Aug 19 '12 at 21:34
Does this answer apply no matter what the file system is? I'm in exactly the same situation as OP, but the partition is HFS+. Is there any difference? I mean, isn't FAT32 more fragmented than HFS? Is it normal for HFS+ to take a long time too?
â Revetahw
May 26 '16 at 6:59
add a comment |Â
Thank you for that well written comprehensive answer. Oh btw,its an external Hard drive.
â Schweinsteiger
Aug 19 '12 at 21:25
@Schweinsteiger You might expect an external drive (depending on the interface) to be somewhat slower than an internal drive, because each access may take a little longer. As for the drive's lifetime, an external drive is actually an internal drive in an enclosure, so the characteristics and design specifications of the internal drive would be what you'd want to consult, if you wanted to determine how suited the drive is to your needs. (Of course, dynamic partitinon resizing operations probably aren't your usual pattern of use.)
â Eliah Kagan
Aug 19 '12 at 21:29
Oh alright. Thanks again :)
â Schweinsteiger
Aug 19 '12 at 21:34
Does this answer apply no matter what the file system is? I'm in exactly the same situation as OP, but the partition is HFS+. Is there any difference? I mean, isn't FAT32 more fragmented than HFS? Is it normal for HFS+ to take a long time too?
â Revetahw
May 26 '16 at 6:59
Thank you for that well written comprehensive answer. Oh btw,its an external Hard drive.
â Schweinsteiger
Aug 19 '12 at 21:25
Thank you for that well written comprehensive answer. Oh btw,its an external Hard drive.
â Schweinsteiger
Aug 19 '12 at 21:25
@Schweinsteiger You might expect an external drive (depending on the interface) to be somewhat slower than an internal drive, because each access may take a little longer. As for the drive's lifetime, an external drive is actually an internal drive in an enclosure, so the characteristics and design specifications of the internal drive would be what you'd want to consult, if you wanted to determine how suited the drive is to your needs. (Of course, dynamic partitinon resizing operations probably aren't your usual pattern of use.)
â Eliah Kagan
Aug 19 '12 at 21:29
@Schweinsteiger You might expect an external drive (depending on the interface) to be somewhat slower than an internal drive, because each access may take a little longer. As for the drive's lifetime, an external drive is actually an internal drive in an enclosure, so the characteristics and design specifications of the internal drive would be what you'd want to consult, if you wanted to determine how suited the drive is to your needs. (Of course, dynamic partitinon resizing operations probably aren't your usual pattern of use.)
â Eliah Kagan
Aug 19 '12 at 21:29
Oh alright. Thanks again :)
â Schweinsteiger
Aug 19 '12 at 21:34
Oh alright. Thanks again :)
â Schweinsteiger
Aug 19 '12 at 21:34
Does this answer apply no matter what the file system is? I'm in exactly the same situation as OP, but the partition is HFS+. Is there any difference? I mean, isn't FAT32 more fragmented than HFS? Is it normal for HFS+ to take a long time too?
â Revetahw
May 26 '16 at 6:59
Does this answer apply no matter what the file system is? I'm in exactly the same situation as OP, but the partition is HFS+. Is there any difference? I mean, isn't FAT32 more fragmented than HFS? Is it normal for HFS+ to take a long time too?
â Revetahw
May 26 '16 at 6:59
add a comment |Â
up vote
1
down vote
Most external drives AFAIK do not have cooling fans, so under the process you described, overheating is expected...and unwanted. There is no need to wear out your hardware before the end of its design lifetime.
I found it quicker and more kind to the hardware, if you copy (not "move") the files to another hard drive temporarily. Or perhaps compress the existing files (7z
, tar
, rar
, or zip
) to one big file, then copy to another drive.
If it's OK to destroy the original files, use GParted (or other disk/partition manager) to immediately reformat the whole drive, defining whatever partitions you want (however many, however big, and whatever filesystems you prefer).
add a comment |Â
up vote
1
down vote
Most external drives AFAIK do not have cooling fans, so under the process you described, overheating is expected...and unwanted. There is no need to wear out your hardware before the end of its design lifetime.
I found it quicker and more kind to the hardware, if you copy (not "move") the files to another hard drive temporarily. Or perhaps compress the existing files (7z
, tar
, rar
, or zip
) to one big file, then copy to another drive.
If it's OK to destroy the original files, use GParted (or other disk/partition manager) to immediately reformat the whole drive, defining whatever partitions you want (however many, however big, and whatever filesystems you prefer).
add a comment |Â
up vote
1
down vote
up vote
1
down vote
Most external drives AFAIK do not have cooling fans, so under the process you described, overheating is expected...and unwanted. There is no need to wear out your hardware before the end of its design lifetime.
I found it quicker and more kind to the hardware, if you copy (not "move") the files to another hard drive temporarily. Or perhaps compress the existing files (7z
, tar
, rar
, or zip
) to one big file, then copy to another drive.
If it's OK to destroy the original files, use GParted (or other disk/partition manager) to immediately reformat the whole drive, defining whatever partitions you want (however many, however big, and whatever filesystems you prefer).
Most external drives AFAIK do not have cooling fans, so under the process you described, overheating is expected...and unwanted. There is no need to wear out your hardware before the end of its design lifetime.
I found it quicker and more kind to the hardware, if you copy (not "move") the files to another hard drive temporarily. Or perhaps compress the existing files (7z
, tar
, rar
, or zip
) to one big file, then copy to another drive.
If it's OK to destroy the original files, use GParted (or other disk/partition manager) to immediately reformat the whole drive, defining whatever partitions you want (however many, however big, and whatever filesystems you prefer).
edited Oct 2 '12 at 19:53
Eliah Kagan
79.2k20218359
79.2k20218359
answered Oct 1 '12 at 11:45
user37991
126117
126117
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f177882%2fshrinking-file-system-taking-a-lot-of-time-is-this-normal%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password