jgrafton: (prompt)
[personal profile] jgrafton
Let it be known: having an openafs cache on ext3 is a bad idea. Especially when you combine it with software suspend 2. I'm wondering if any of my filesystem will be salvagable after this... sigh. Sucks. A lot.

e2fsck has been running for a while now... just waiting for it to say

"Your filesystem is fucked. Clear<y>?"

I really should be working on 212, too, but (clearly) not in the right mood at the moment.

(I suppose Windows will still work, hopefully, but still. Bah.)

(no subject)

Date: 2005-11-16 05:07 am (UTC)
From: [identity profile] mr-wright.livejournal.com
Doesn't the openafs cache just consist of regular files, as far as the filesystem is concerned? I'm kind of confused about why that would be a bad combination.

(no subject)

Date: 2005-11-16 05:39 am (UTC)
From: [identity profile] experiment6.livejournal.com
Presumably kernel swsusp + openafs + ext3 caused some sort of confusion, although I'm curious myself as to what happened and why ext3 was a problem?

(no subject)

Date: 2005-11-18 01:43 am (UTC)
From: (Anonymous)
ext3 is supposed to work, however. And it's only one of like three filesystems that do work, it seems like it should. All syslab machines have been running AFS cache out of ext3 since you implemented it. You sure it was ext3?

-Deason

Profile

jgrafton: (Default)
Jeff Grafton

January 2017

S M T W T F S
1234567
891011 12 1314
15161718192021
22232425262728
293031    

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags