On 5-Mar-2009, at 20:12, LuKreme wrote:
> On 5-Mar-2009, at 19:22, Milo Velimirović wrote:
>> After you unmount /dev/backup run an fsck against it. You may need to
>> tell it to use an alternate superblock if the default one is
>> corrupted or unavailable. i.e.,
>
> $ fsck /dev/ad1s1c
> ** /dev/ad1s1c (NO WRITE)
> ** Last Mounted on /backup
> ** Phase 1 - Check Blocks and Sizes
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> ** Phase 5 - Check Cyl groups
> 2095403 files, 55964850 used, 19719503 free (114975 frags, 2450566
> blocks, 0.2% fragmentation)
> $ tunefs -m 1 -o space /dev/ad1s1c
> tunefs: minimum percentage of free space changes from 8% to 1%
> tunefs: should optimize for space with minfree < 8%
> tunefs: optimization preference changes from time to space
> tunefs: /dev/ad1s1c: failed to write superblock
> $
>
> I will try dropping to single-user mode this weekend and see if that
> makes a difference.
Bah, I have to be onsite to do that. This is going to be more
complicated than I first thought. Maybe I'll just leave it alone for
now. Not sure it's worth the effort. All I have to do is change the
process that write the backup IMAP folder to be a root process and
I'll avoid any problems with free space anyway. No users have access
to that drive anyway.
--
In my world there are people in chains and you can ride them like
ponies
_______________________________________________
OSX-Nutters mailing list | [email protected]
http://lists.tit-wank.com/mailman/listinfo/osx-nutters
List hosted at http://cat5.org/
