Reputation
6,390
Top tag
Next privilege 10,000 Rep.
Access moderator tools
Badges
5 22 46
Newest
 Yearling
Impact
~1.0m people reached

Apr
30
comment Create Logical Volume Snapshot at boot and before mount
This facility does require that the snapshot be made at a time when the data on the logical volume is in a consistent state - the VFS-lock patch for LVM1 makes sure that some filesystems do this automatically when a snapshot is created, and many of the filesystems in the 2.6 kernel do this automatically when a snapshot is created without patching. tldp.org/HOWTO/LVM-HOWTO/snapshotintro.html - But for a consisten file backup, applications must write their buffers to disk or be closed.
Apr
30
comment Create Logical Volume Snapshot at boot and before mount
Do you have a references stating LVM2 being sufficiently aware of the filesystem to always create snapshots with a consistent filesystem?
Apr
29
comment sda and sdb block specials point to same device and get mixed up (hardware RAID doesn't work after new installation of 12.04)
Are you using md? What is the output to sudo mdadm --detail /dev/md*? And the output of cat /proc/partitions
Apr
29
comment Throttling web crawlers
OK, it looks pretty simple. Implemented it to see if my webserver wil be able to keep up now.
Apr
28
comment How to install daemontools on ubuntu or debian from source
Why do you want to install daemontools on your Linux machine? What good stuff does it bring?
Apr
27
comment Throttling web crawlers
Looks a bit more complicated than I'd hoped for on a friday evening enjoying Belgian beer ... Have to look at it tomorrow. Looks promising with the browsermatch and things. Coming to think of it ... would be nice if it automatically any host / useragent that requests robot.txt :o) Thnx Uther
Apr
27
comment Grow/resize RAID when upgrading visible size of disks
Strange, I'm sure having seen warning when I was replacing disks. I exchanged my 750GB drives with 1TB drives about a year ago. Does sudo mdadm --examine /dev/sdx give proper results?
Apr
27
comment Grow/resize RAID when upgrading visible size of disks
See my comment above: "mdadm will warn you that you're trying to add a device that is much larger than the other ones."
Apr
26
comment Grow/resize RAID when upgrading visible size of disks
You have up to 36T data stored, please be careful and make backups.
Apr
26
comment Grow/resize RAID when upgrading visible size of disks
You can fail a drive, then remove it, then zero-superblock it to remove the metadata. As your RAID set is in use you can either add it as a spare, which means it won't sync until another drive fails (that is normal behavior) but it only works for a single drive OR you add it and it requires a sync. I know it takes forever. Or you accept the fact that you cannot addres all storage available. One of the advantages of using a partition table which you didn't. Not using a partition table is not bad, but in this particular case would have helped you.
Apr
26
comment Grow/resize RAID when upgrading visible size of disks
Oh, I understand your question. mdadm will warn you that you're trying to add a device that is much larger than the other ones. It doesn't mind about a few bytes, but it warns you when it the difference is relatively large.
Apr
26
comment Grow/resize RAID when upgrading visible size of disks
No I haven't tested this, but I've seen some md problems before and I have some feeling about how it works ... and fails. I don't have the drives with bad metadata lying around to test it. I'm aware of the long sync time, that is why I advise to use the spare. You have RAID6, which means 2 drives can fail and you have a spare. That means a total of 3 drives that can fail before you have a problem. You could check with a single drive, at least you know if this is your issue. I have only limited information about your setup. Don't pull drives from your RAID set if you're not comfortable doing it
Apr
25
comment console space eaten up by file contents
Not all distributions use RPM package manager, so that is useless information as long as we don't know the distribution.
Apr
25
comment console space eaten up by file contents
vim is called with vi from the command line. Many distributions, including Ubuntu, have vim-tiny installed by default which again is simply called from the command line by typing vi. One of the habits of vim-tiny is the effect as described above.
Apr
25
comment Location on disk to write a byte-flag?
Is an extended partition no option?
Apr
24
comment “error: no such device” at boot in Ubuntu Server 11.10 with Raid1
You might want to check cat /proc/mdstat. Both RAID sets should show up, including rebuilding progress.
Apr
23
comment Fork bomb on a Mac?
My conclusion is that I'm über-smart ;o) Personally I'd rather higher a limit when I need it than accidentally crashing my system because of a typo. And you are right about the file. I always confuse the two.
Apr
23
comment Fork bomb on a Mac?
Maybe good to mention: the ulimit can be made to survive a reboot by configuring it in /etc/sysctl.conf.
Apr
23
comment Fork bomb on a Mac?
Still I think it is a foolish default that most distributions allow a fork bomb from unprivileged users to DoS a machine.
Apr
23
comment Fork bomb on a Mac?
foolish me ... apropos rlimit gives nice hints :)