Re: skip fsck when booting on battery?
On Mon, 2011-02-07 at 20:59 +0100, Steven wrote: [snipped discussion about slow fsck on large ext3 partitions] Or would in this case another file system be a better option for the large partitions? Ext4 comes to mind. The system is not backed by a UPS so power failures do happen (although not often). ext4 would certainly solve the slow fsck problem; it's prety much instant on a cleanly shut down file system. I haven't heard anything about ext4 journaling being inherently less robust that ext3, though there were lots of discussions about the 'right' mount options for robustness/performance tradeoffs. Might be worth researching. -- Tixy () The ASCII Ribbon Campaign (www.asciiribbon.org) /\ Against HTML e-mail and proprietary attachments -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1297157311.1897.33.camel@ubuntu
Re: skip fsck when booting on battery?
On Mon, Feb 07, 2011 at 08:59:15PM +0100, Steven wrote: An interesting view, I'll keep it in mind when/if reinstalling the laptop, it has 2 physical drives, each 160 GB. Only the first one is slightly less due to a swap partition. Currently the whole disk is used for /, and the second one is mounted somewhere on /media. Now considering a desktop system like mine, how would that play out? The system has a 2GB /boot partition on an SSD, and / is the remaining of that SSD (let's say 57GB). A partition of another regular drive is used as /home (476GB). Then there are 2 md raid arrays, each consisting of 2 drives 1TB in size, raid 1 (mirror), both mounted as data arrays under /media. All file systems are ext3. Obviously the SSD is quite fast when checking so not an issue, /home however takes about 15 minutes, and each raid array approximately 45 minutes. Or would in this case another file system be a better option for the large partitions? Ext4 comes to mind. The system is not backed by a UPS so power failures do happen (although not often). Such large arrays hold all kinds of data, from large images (both cd, dvd and hard drives of over 120 GB) to small text files. Thank you for your time. Nice sounding system. I am more the old notebook enthusiast/hobbyist though. I would worry about ramifications of partitioning solid state drives without research. I haven't had any problems with ext4 that I am aware of yet. Regarding RAID, I have read that partitioning is advantageous for expansions. But that remains contingent on the controller, the level, the implementation and the objective. Again, I just started looking at the possibility of a RAID storage in the far future! Many discussion to Google on that! -- Regards, Freeman Microsoft is not the answer. Microsoft is the question. NO (or Linux) is the answer. --Somebody -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110208214012.GA9047@Europa.office
Re: skip fsck when booting on battery?
On Sun, 2011-02-06 at 17:40 -0800, Freeman wrote: On Mon, Feb 07, 2011 at 12:47:52AM +0100, Steven wrote: . . . @ elbbit: The file system is ext3, however I wouldn't turn of the automatic routine checks entirely. I think I'll just leave it as it is and see if Ctrl+C does the trick, when I'm at home I'll just let it finish, it doesn't take that long, and use my desktop instead (now _that_ takes long, checking multiple 1TB disks). In the name of sucking some more marrow out of that little bone, there is a way to edit file system parameters to near insignificance at boot checks without severely reducing effectiveness. With a strategy of multiple partitions facilitating staggered backups, security, disk checks and whatever, varying check intervals can be assigned to each partition according to priority. So given /boot, /srv, /, /home, /usr, /usr/share, and /var, all assigned to different partitions in a rambling /etc/fstab, Where checking /srv is the highest priority and /boot, the least priority, Figure the desired boot interval for checking /srv and assign the closest prime number, say 29, tune2fs -c 29 /dev/designation_for_/srv_partition Work up the list of prime numbers respectively. Now, checking /boot (250M ?), will take a second or so every 53 boots. Even /srv or /home (7-10G ?) would be way less trouble than the entire drive. An interesting view, I'll keep it in mind when/if reinstalling the laptop, it has 2 physical drives, each 160 GB. Only the first one is slightly less due to a swap partition. Currently the whole disk is used for /, and the second one is mounted somewhere on /media. Now considering a desktop system like mine, how would that play out? The system has a 2GB /boot partition on an SSD, and / is the remaining of that SSD (let's say 57GB). A partition of another regular drive is used as /home (476GB). Then there are 2 md raid arrays, each consisting of 2 drives 1TB in size, raid 1 (mirror), both mounted as data arrays under /media. All file systems are ext3. Obviously the SSD is quite fast when checking so not an issue, /home however takes about 15 minutes, and each raid array approximately 45 minutes. Or would in this case another file system be a better option for the large partitions? Ext4 comes to mind. The system is not backed by a UPS so power failures do happen (although not often). Such large arrays hold all kinds of data, from large images (both cd, dvd and hard drives of over 120 GB) to small text files. Thank you for your time. Kind regards, Steven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1297108755.3903.21.ca...@pc-steven.lan
Re: skip fsck when booting on battery?
On 06/02/11 19:48, Steven wrote: Hi, Earlier today at fosdem, I was booting my laptop and it started a routine file system check (booted 28 times without being checked, check forced). Obviously I don't want the laptop doing that check when it's on battery power, especially since it has an aging battery. How do I turn I fix this, or is this a bug? The laptop is an Acer Aspire 7720G running Debian Squeeze. I do notice that the laptop seems to 'think' it was still on AC power until later in the boot sequence, due to the brightness setting. I think it keeps the previous AC/battery state from last boot, and only checks again quite late in the boot process. Any ideas are welcome. Kind regards, Steven tibz@ice ~ $ apropos tune2fs tune2fs (8) - adjust tunable filesystem parameters on ext2/ext3/ext4 filesystems tibz@ice ~ $ man 8 tune2fs Particularly you are interested in the -c and -i switches. This is assuming of course that the partition being checked is an ext2/3/4. -- elbbit -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d4f16ac.5040...@gmail.com
Re: skip fsck when booting on battery?
On Sun, Feb 06, 2011 at 08:48:23PM +0100, Steven wrote: Hi, Earlier today at fosdem, I was booting my laptop and it started a routine file system check (booted 28 times without being checked, check forced). Obviously I don't want the laptop doing that check when it's on battery power, especially since it has an aging battery. How do I turn I fix this, or is this a bug? There is a power status section near the top of checkfs.sh that is commented out citing bug #526398. The script runs from init.d in runlevel S, /etc/rcS.d . The laptop is an Acer Aspire 7720G running Debian Squeeze. You should be able to get out of checks with CTRL-C . I do notice that the laptop seems to 'think' it was still on AC power until later in the boot sequence, due to the brightness setting. I think it keeps the previous AC/battery state from last boot, and only checks again quite late in the boot process. Maybe that is acpi starting in runlevel 2 or whatever runlevel you end up in. -- Regards, Freeman Microsoft is not the answer. Microsoft is the question. NO (or Linux) is the answer. --Somebody -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110206214958.GA4508@Europa.office
Re: skip fsck when booting on battery?
On Sun, 2011-02-06 at 13:49 -0800, Freeman wrote: On Sun, Feb 06, 2011 at 08:48:23PM +0100, Steven wrote: Hi, Earlier today at fosdem, I was booting my laptop and it started a routine file system check (booted 28 times without being checked, check forced). Obviously I don't want the laptop doing that check when it's on battery power, especially since it has an aging battery. How do I turn I fix this, or is this a bug? There is a power status section near the top of checkfs.sh that is commented out citing bug #526398. The script runs from init.d in runlevel S, /etc/rcS.d . Thanks for pointing out that bug, I'm not sure what to do with it, re-enabling it is fairly safe as long as I remember not to boot from battery after a failure. Then again, should I trust my memory not to forget that?... The laptop is an Acer Aspire 7720G running Debian Squeeze. You should be able to get out of checks with CTRL-C . Hmm.. good point, haven't tried that yet, Esc didn't work, but that was a couple of years ago on another distribution. I do notice that the laptop seems to 'think' it was still on AC power until later in the boot sequence, due to the brightness setting. I think it keeps the previous AC/battery state from last boot, and only checks again quite late in the boot process. Maybe that is acpi starting in runlevel 2 or whatever runlevel you end up in. Perhaps it's only the brightness, in that case I can live with it, I'll look into it a bit further when I have the time. @ elbbit: The file system is ext3, however I wouldn't turn of the automatic routine checks entirely. I think I'll just leave it as it is and see if Ctrl+C does the trick, when I'm at home I'll just let it finish, it doesn't take that long, and use my desktop instead (now _that_ takes long, checking multiple 1TB disks). Thank you both for replying. Kind regards, Steven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1297036072.6025.13.ca...@pc-steven.lan
Re: skip fsck when booting on battery?
On Mon, Feb 07, 2011 at 12:47:52AM +0100, Steven wrote: . . . @ elbbit: The file system is ext3, however I wouldn't turn of the automatic routine checks entirely. I think I'll just leave it as it is and see if Ctrl+C does the trick, when I'm at home I'll just let it finish, it doesn't take that long, and use my desktop instead (now _that_ takes long, checking multiple 1TB disks). In the name of sucking some more marrow out of that little bone, there is a way to edit file system parameters to near insignificance at boot checks without severely reducing effectiveness. With a strategy of multiple partitions facilitating staggered backups, security, disk checks and whatever, varying check intervals can be assigned to each partition according to priority. So given /boot, /srv, /, /home, /usr, /usr/share, and /var, all assigned to different partitions in a rambling /etc/fstab, Where checking /srv is the highest priority and /boot, the least priority, Figure the desired boot interval for checking /srv and assign the closest prime number, say 29, tune2fs -c 29 /dev/designation_for_/srv_partition Work up the list of prime numbers respectively. Now, checking /boot (250M ?), will take a second or so every 53 boots. Even /srv or /home (7-10G ?) would be way less trouble than the entire drive. -- Regards, Freeman Microsoft is not the answer. Microsoft is the question. NO (or Linux) is the answer. --Somebody -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110207014055.GA12118@Europa.office
