Oh - and admittedly, one of the directories in the problem partition
has over smaller 5000+ files in it:
=-=-=-=-=-=-=-
# ls -al | wc -l
5131
#
# ls -al
total 468
drwxrwxr-x 7 name name 512 Apr 4 21:27 .
drwxrwxr-x 3 name name 512 Apr 4 21:11 ..
drwxr-xr-x 2 name name 88064 Apr 4 21:27 Folder
drwxr-xr-x 2 name name 512 Apr 4 21:27 conversations
drwxrwxr-x 2 name name 140288 Apr 4 21:25 graphics
drwxr-xr-x 4 name name 512 Apr 4 21:27 shorts
drwxrwxr-x 8 name name 512 Apr 4 21:23 lists
#
=-=-=-=-=-=-=-
Cheers!
On 08/04/06, Whyzzi <[EMAIL PROTECTED]> wrote:
> On 08/04/06, Otto Moerbeek <[EMAIL PROTECTED]> wrote:
> >
> > On Fri, 7 Apr 2006, Whyzzi wrote:
> >
> > > On 07/04/06, Otto Moerbeek <[EMAIL PROTECTED]> wrote:
> > > >
> > > > On Thu, 6 Apr 2006, Whyzzi wrote:
> > > >
> > > > > Yeah! that is the thing I didn't do! Run fsck against the affected
> > > > > partition! Anyways, as per your questions:
> > > > >
> > > > > I copied the with cp, eg:
> > > > > # cd /mnt/wd1a
> > > > > # cp -R Anime /mnt/wd2d
> > > > >
> > > > > Here are the raw df output from the current snapshot kernel [brought
> > > > > to you by the wonders of OpenSSH]:
> > > > > # df
> > > > > Filesystem 512-blocks Used Avail Capacity Mounted on
> > > > > /dev/wd0a 18572172 1062820 16580744 6% /
> > > > > /dev/wd0d 123841300 4215514788 197101744 14535% /mnt/wd0d
> > > > > /dev/wd0e 123841300 13434788 104214448 11% /mnt/wd0e
> > > > > /dev/wd0f 212356232 66929816 134808608 33% /mnt/wd0f
> > > > > #
> > > > >
> > > > > I had torrent'd the Olive OpenBSD live cd awhile back that was a
> > > > > December? -stable 3.8 (I think), could I use that to run fsck against
> > > > > the affected partition? That would be easier to do than to hookup the
> > > > > 40gig that contained the Dec snapshot (I don't have a copy of either
> > > > > 3.8/3.9 -release available, but I will make one and install it if you
> > > > > want me to).
> > > >
> > > > The Olive CD will probably do, although booting a 3.8 kernel from the
> > > > boot prompt should work as well; just copy the 3.8 kernel to your root
> > > > as bsd38 and type "boot bsd38" at the boot prompt.
> > >
> > > Cool. Done. I used ftp to grab the 3.8 release kernel from a local
> > > mirror. I booted single user mode cause I didn't want my services
> > > spewing at me due to kernel differences. Below are the results:
> > > =-=-=-=-=-=-=-=-=-=-=-=-
> > > boot> boot /bsd.38 -s
> > >
> > > /** SNIP -- cause I copied everything by hand **/
> > >
> > > Enter pathname or RETURN for shell:
> > > Terminal type? vt220
> > > # dh -h
> > > Filesystem Size Used Avail Capacity Mounted on
> > > root_device 8.9G 524M 7.9G 6% /
> > > # mount /dev/wd0d /mnt/wd0d
> > > # df
> > > Filesystem 512-blocks Used Avail Capacity Mounted on
> > > root_device 18572127 1073632 16569932 6% /
> > > /dev/wd0d 123841300 4215514788 197101744 14535% /dev/wd0d
> > > =-=-=-=-=-=-=-=-=-=-=-=-
> > > Interesting. No difference whatsoever. And because I am a (l)user, I
> > > am not going to even try to theorize what happened and why. The only
> > > thing I will say is that each directory I copied - there were five,
> > > all contained literally more than 10Gigabytes (usually more) of
> > > useless data each (ok the mp3 collection isn't so useless).
> > >
> > > This might be reproduce-able by creating 20 or so 500MB files and
> > > stuffing them into various subdirectories, totalling 10Gb in one
> > > directory. copy that 5 times by giving the same directory a different
> > > name. Then take a look at the drive stats via df. Just remember that
> > > in my case the destination partition was mounted sync.
> > >
> > > Is there anything you would like to have done - or can I use the 3.9
> > > snapshot and run the fsck?
> > >
> > > Cheers, & thanks!
> >
> > To be on the safe side, run a 3.8 fsck. Easiest way to do that is copy
> > a 3.8 bsd.rd and boot that. Go to the shell and run fsck -f.
> >
> > -Otto
> >
>
> Done. Followed http://www.openbsd.org/faq/faq4.html#bsd.rd part of the
> FAQ, and ripped the 3.8 bsd.rd from the usa.openbsd.org server. Just
> for info, the bsd.38.rd reports the same df as the others...
>
> Ok, this is strange:
> =-=-=-=-=-=-=-=-=-
> # fsck /dev/rwd0d
> ** /dev/rwd0d
> ** File system is clean; not checking
> # fsck -f /dev/rwd0d
> ** /dev/rwd0d
> ** File system is already clean
> cannot alloc 4294966928 bytes for inphead
> # fsck -f /dev/wd0d
> ** /dev/wd0d
> ** File system is already clean
> cannot alloc 4294966928 bytes for inphead
> #
> =-=-=-=-=-=-=-=-=-
>
> I hope that helps some.. If there is anything else you'd like from
> this box just let me know!
>
--
I know too much and yet not enough
