Re: Odd df reporting (On Apr 3 snapshot, data copied via 3.8snapshot)

2006-04-21 Thread Whyzzi
Cool! That seems to have done the trick (April 20, 2006 snapshot): (I)nstall, (U)pgrade, or (S)hell? s # fsck -b32 -f /dev/rwd0d Alternate Superblock Location: 32 ** /dev/rwd0d ** File system is already clean ** Last mounted on ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames **

Re: Odd df reporting (On Apr 3 snapshot, data copied via 3.8snapshot)

2006-04-13 Thread Whyzzi
Could I conceivably download the latest snapshot bsd.rd and check that way, rather than upgrading my existing system? On 13/04/06, Pedro Martelletto [EMAIL PROTECTED] wrote: And a fresh kernel too :-)

Re: Odd df reporting (On Apr 3 snapshot, data copied via 3.8snapshot)

2006-04-09 Thread Otto Moerbeek
On Sat, 8 Apr 2006, Whyzzi wrote: 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

Re: Odd df reporting (On Apr 3 snapshot, data copied via 3.8snapshot)

2006-04-09 Thread Pedro Martelletto
It would be wise to actually force the checking by specifying -f. -p.

Re: Odd df reporting (On Apr 3 snapshot, data copied via 3.8snapshot)

2006-04-08 Thread Otto Moerbeek
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

Re: Odd df reporting (On Apr 3 snapshot, data copied via 3.8snapshot)

2006-04-08 Thread Whyzzi
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

Re: Odd df reporting (On Apr 3 snapshot, data copied via 3.8snapshot)

2006-04-08 Thread Whyzzi
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

Re: Odd df reporting (On Apr 3 snapshot, data copied via 3.8snapshot)

2006-04-07 Thread Otto Moerbeek
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

Re: Odd df reporting (On Apr 3 snapshot, data copied via 3.8snapshot)

2006-04-07 Thread Whyzzi
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

Re: Odd df reporting (On Apr 3 snapshot, data copied via 3.8snapshot)

2006-04-06 Thread Otto Moerbeek
On Wed, 5 Apr 2006, Whyzzi wrote: I've had a strange occurance I'd like to report, in using df -h, but the circumstances that brought about this condition are somewhat unusual, so I really don't know if it is anything to be concerned about. This might also have already been fixed, as I do not

Re: Odd df reporting (On Apr 3 snapshot, data copied via 3.8snapshot)

2006-04-06 Thread Whyzzi
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