He also said the superblocks are different, so you can't expect anything
(df, mount, fsck) to work.
-p.
Ted said running fsck on them might break them. But that's not what I
asked. I was referring to my original problem of the weird sizes in
df.
On 6/12/06, Pedro Martelletto <[EMAIL PROTECTED]> wrote:
Please read again what Ted wrote.
-p.
--
NetBSD/i386 3.0 + pkgsrc-current | OpenBSD/
Please read again what Ted wrote.
-p.
> > I thought maybe something's corrupt, and so tried doing an "fsck -f
> > /dev/wd0g". I get the following:
> >
> > ** /dev/rwd0g
> > ** File system is already clean
> > cannot alloc 4294966956 bytes for inphead
> >
> > I figure doing an fsck might set things right, but the above error stops me.
> I thought maybe something's corrupt, and so tried doing an "fsck -f
> /dev/wd0g". I get the following:
>
> ** /dev/rwd0g
> ** File system is already clean
> cannot alloc 4294966956 bytes for inphead
>
> I figure doing an fsck might set things right, but the above error stops me.
>
> The partitio
On 6/11/06, Rakhesh Sasidharan <[EMAIL PROTECTED]> wrote:
/dev/wd0g 4786774 4294886268 4628464 188894%/mnt/nbsd
Any ideas why /dev/wd0g is showing up with that weird capacity and sizes?
Here's the relevant entry for it from my disklabel:
g: 9724176 21430710 4.2BSD 204
Hi,
Check out this "df" output:
Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/wd0g 4786774 4294886268 4628464 188894%/mnt/nbsd
Any ideas why /dev/wd0g is showing up with that weird capacity and sizes?
Here's the relevant entry for it from my disklabel:
g:
7 matches
Mail list logo
