1 |
On 26 February 2010 12:33, Mark Knecht <markknecht@×××××.com> wrote: |
2 |
> So I got my wife's machine booted today using a install disk and |
3 |
> played a bit with e2fsck. The machine stopped being happy last night |
4 |
> due to some sort of corruption on the /var partition. e2fsck |
5 |
> complained about 3 or 4 files and then repaired the partition. The |
6 |
> machine booted cleanly as far as I can tell. |
7 |
|
8 |
Hey buddy! |
9 |
|
10 |
This happened to me, too! See below for my savage ranting for a good laugh. |
11 |
|
12 |
My rule for this is rsnapshot my present system as it is, grab a disk |
13 |
image backup (taken less frequently), and then go to town with |
14 |
portage. |
15 |
|
16 |
I emerged 620 packages today. (Much more in fact if I count |
17 |
rebuilding and stuff.) Only OO.o update is remaining in world. |
18 |
|
19 |
I don't think there's a good and safe way around it. I find inode |
20 |
corruption can be sneaky and hit other stuff. Assuming your backs all |
21 |
exist and stuff, then you can hit up stuff like rsync with the update |
22 |
flag for your personal files between newest and safest backups. |
23 |
|
24 |
Rant: |
25 |
Okay, so Mac OS is getting it to the face now, officially, and forever |
26 |
in my world. I've almost kind of said this before, and I can't |
27 |
remember why I don't follow my own advice, but nothing can be worse |
28 |
than twice-monthly 10% inode corruption. |
29 |
|
30 |
Now check this out: |
31 |
The e2fs program is told "do not mount sda3" and "if you ever do, |
32 |
mount it ro." Even though Mac OS is crazy enough not to use |
33 |
/etc/fstab, it will still (supposedly) listen to rules in here. I |
34 |
found some very retarded way of effectively serial-device referencing |
35 |
sda3, and I said, "do not mount this drive at boot, and if you do, do |
36 |
it ro." Then I went into a Disk Utility thing. I told that the same |
37 |
thing. So that's three times I've said, "Never touch this drive with |
38 |
a 10 foot pole, plz thx!" Yeah, please explain to me how an |
39 |
unmounted, only ro drive can receive rectal examination of 11.4% |
40 |
inode corruption. |
41 |
|
42 |
Others, please take this as a lesson (in some form or another). I |
43 |
think it's the badly coded e2fs program, but that thing is so bad that |
44 |
if it is to blame, it happened after I tried to uninstall the program |
45 |
too, so who knows. So I'm going to put a tiny Tiger install this |
46 |
weekend so I can get nice boot, a few firmware accesses (kill the |
47 |
silly booting sound, and delay an annoying 20 second boot delay in the |
48 |
case there is no EFI partition...ugh). And then I am going to never |
49 |
look at it's ugly face again. |
50 |
|
51 |
System Rescue CD, partimage, and rsnapshot are my friends! |
52 |
|
53 |
(I had so many packages because over the holidays I didn't do sync and |
54 |
world updates, and then I decided to go back to the wonderful ~x86, |
55 |
but since I was super busy and I don't like backing up a system that's |
56 |
untested, then I didn't have good backups of the updates. Maybe a |
57 |
poor choice, but in any case, that was not the reason I was trying to |
58 |
kick myself in the face. |
59 |
|
60 |
Be bloody lucky, |
61 |
or don't use retarded softwarez--- |
62 |
daid |
63 |
|
64 |
> |
65 |
> So, something went bad and I managed to sneak around it for a while |
66 |
> and now I'm sort of living with the machine wondering what to do. |
67 |
> |
68 |
> Do I just watch the logs looking for problems? I have no way of |
69 |
> knowing right now whether this was a disk problem that's going to come |
70 |
> back, a 1 time deal due to power, or something else entirely. |
71 |
> |
72 |
> As these cheap machines that don't use RAID what's the right way to |
73 |
> go? emerge -e @world and then wait for the next event? Do nothing and |
74 |
> wait? |
75 |
> |
76 |
> We've got decent personal data backups as well as basic /etc data. |
77 |
> |
78 |
> Thanks, |
79 |
> Mark |
80 |
> |
81 |
> |