On Thu, 2007-03-29 at 07:37 -0800, Peter A. Giessel wrote:
> On 2007/03/28 19:47, Pieter de Goeje seems to have typed:
> > On woensdag 28 maart 2007, Dan D Niles wrote:
> >> I am trying to fsck a 6T filesystem on a server that crashed. I'm
> >> running FreeBSD 6.2-p3.
> >>
> >> # fsck -t ufs -y /d
On Thu, 2007-03-29 at 05:47 +0200, Pieter de Goeje wrote:
> On woensdag 28 maart 2007, Dan D Niles wrote:
> > I am trying to fsck a 6T filesystem on a server that crashed. I'm
> > running FreeBSD 6.2-p3.
> >
> > # fsck -t ufs -y /dev/da0
> > fsck_ufs: cannot alloc 1993797728 bytes for inoinfo
> C
On 2007/03/28 19:47, Pieter de Goeje seems to have typed:
> On woensdag 28 maart 2007, Dan D Niles wrote:
>> I am trying to fsck a 6T filesystem on a server that crashed. I'm
>> running FreeBSD 6.2-p3.
>>
>> # fsck -t ufs -y /dev/da0
>> fsck_ufs: cannot alloc 1993797728 bytes for inoinfo
> Could y
On woensdag 28 maart 2007, Dan D Niles wrote:
> I am trying to fsck a 6T filesystem on a server that crashed. I'm
> running FreeBSD 6.2-p3.
>
> # fsck -t ufs -y /dev/da0
> fsck_ufs: cannot alloc 1993797728 bytes for inoinfo
Could you run 'limits' here? I suspect 'datasize' is too low.
Regards,
Pi
On Wed, 2007-03-28 at 20:21 -0500, Josh Paetzel wrote:
> Dan D Niles wrote:
> > I am trying to fsck a 6T filesystem on a server that crashed. I'm
> > running FreeBSD 6.2-p3.
> >
> > # fsck -t ufs -y /dev/da0
> > fsck_ufs: cannot alloc 1993797728 bytes for inoinfo
> >
> > I also tried:
> >
> > #
Dan D Niles wrote:
> I am trying to fsck a 6T filesystem on a server that crashed. I'm
> running FreeBSD 6.2-p3.
>
> # fsck -t ufs -y /dev/da0
> fsck_ufs: cannot alloc 1993797728 bytes for inoinfo
>
> I also tried:
>
> # fsck -t ufs -f -p /dev/da0
> /dev/da0: UNKNOWN FILE TYPE I=11895232
> /dev
I am trying to fsck a 6T filesystem on a server that crashed. I'm
running FreeBSD 6.2-p3.
# fsck -t ufs -y /dev/da0
fsck_ufs: cannot alloc 1993797728 bytes for inoinfo
I also tried:
# fsck -t ufs -f -p /dev/da0
/dev/da0: UNKNOWN FILE TYPE I=11895232
/dev/da0: UNEXPECTED INCONSISTENCY; RUN fsck