On 11/28/05, Tan Dang <[EMAIL PROTECTED]> wrote:
> I have had this problem of files not showing up on the fat partition
> after moving the files over from ffs also. I dual boot OpenBSD 3.8
> and Windows XP on my laptop. Both os's share a fat partition. For my
> particular case, I put Windows XP
On Mon, 28 Nov 2005, Tan Dang wrote:
I have had this problem of files not showing up on the fat partition
after moving the files over from ffs also. I dual boot OpenBSD 3.8
and Windows XP on my laptop. Both os's share a fat partition. For my
particular case, I put Windows XP into hibernation
On Mon, Nov 28, 2005 at 09:47:25PM -0600, Tan Dang wrote:
> I dual boot OpenBSD 3.8
> and Windows XP on my laptop. Both os's share a fat partition. For my
> particular case, I put Windows XP into hibernation mode and booted to
> OpenBSD. I copied some ogg files from the ffs partition to the
On 11/28/05, Ted Unangst <[EMAIL PROTECTED]> wrote:
> On 11/27/05, frantisek holop <[EMAIL PROTECTED]> wrote:
> > > it shouldn't. you might get files landing in the wrong directory (i'm
> > > not really sure this is possible either, but it's probably the worst
> > > that could happen), but there s
On 11/27/05, frantisek holop <[EMAIL PROTECTED]> wrote:
> > it shouldn't. you might get files landing in the wrong directory (i'm
> > not really sure this is possible either, but it's probably the worst
> > that could happen), but there shouldn't be any real disk corruption.
>
>
> i had files not
hmm, on Sun, Nov 27, 2005 at 12:24:14AM -0800, Ted Unangst said that
> On 11/27/05, Alexander Hall <[EMAIL PROTECTED]> wrote:
> > I was wondering if this could cause a lot of other errors, like
> > corrupted files and such. I am thinking about if I dare to mount and use
> > msdos filesystems r/w ag
On 11/27/05, Alexander Hall <[EMAIL PROTECTED]> wrote:
> I was wondering if this could cause a lot of other errors, like
> corrupted files and such. I am thinking about if I dare to mount and use
> msdos filesystems r/w again... But then again, if noone dares to do it,
> we'll never know if it work
Pedro Martelletto wrote:
On Sat, Nov 26, 2005 at 01:45:47AM -0800, Ted Unangst wrote:
there may be a missing cache_purge in msdosfs_rename.
I've looked at the code and yes, you're correct. There was a missing
cache_purge() in msdosfs_rename(), and that fixed the issue for me.
Alexander, can
On Sat, Nov 26, 2005 at 01:45:47AM -0800, Ted Unangst wrote:
> there may be a missing cache_purge in msdosfs_rename.
I've looked at the code and yes, you're correct. There was a missing
cache_purge() in msdosfs_rename(), and that fixed the issue for me.
Alexander, can you confirm the problem is g
On 11/25/05, Alexander Hall <[EMAIL PROTECTED]> wrote:
> $ mkdir a aa ab
> $ find .
> .
> ./a
> ./aa
> ./ab
> $ mv aa ab a
> $ find .
> .
> ./a
> ./a/aa
> $ ll a
> total 16
> drwxrwxrwx 1 root wheel 4096 Nov 26 00:52 aa/
> drwxrwxrwx 1 root wheel 4096 Nov 26 00:52 ab/
> $ find -L .
> .
> ./a
On Sat, Nov 26, 2005 at 03:05:30AM +0100, Alexander Hall wrote:
> Actually, after testing copying aa and ab separately, I cannot reproduce
> the previous errors again. Maybe a reboot will "help".
>
> FWIW, I think that unmounting and mounting the fs again restored the
> order (or so it seemed).
Pedro Martelletto wrote:
On Sat, Nov 26, 2005 at 12:57:06AM +0100, Alexander Hall wrote:
$ dd if=/dev/zero of=msdos_fs bs=1024 count=1024
$ sudo vnconfig vnd0 msdos_fs
$ sudo newfs_msdos /dev/rvnd0c
$ sudo mount_msdos -m 777 -l /dev/vnd0c /mnt/test/
$ cd /mnt/test
$ mkdir a aa ab
$ find .
.
On Sat, Nov 26, 2005 at 12:57:06AM +0100, Alexander Hall wrote:
> $ dd if=/dev/zero of=msdos_fs bs=1024 count=1024
> $ sudo vnconfig vnd0 msdos_fs
> $ sudo newfs_msdos /dev/rvnd0c
> $ sudo mount_msdos -m 777 -l /dev/vnd0c /mnt/test/
> $ cd /mnt/test
> $ mkdir a aa ab
> $ find .
> .
> ./a
> ./aa
>
On Sat, Nov 26, 2005 at 12:57:06AM +0100, Alexander Hall wrote:
> I ran into this just this week while moving stuff like crazy. Succeeded
> to boil stuff down to a very limited set of operations that fscks things
> up. I run tests on a (disposable :) vnd device but I got the same
> results on an
A long time ago, Pedro Martelletto wrote:
Alexander, can you please try to build a test-case that rules out NFS,
if at all possible?
I ran into this just this week while moving stuff like crazy. Succeeded
to boil stuff down to a very limited set of operations that fscks things
up. I run test
hmm, on Sat, Oct 08, 2005 at 10:50:01AM +0100, Tom Cosgrove said that
> >>> frantisek holop 29-Sep-05 01:23 >>>
> >
> > hmm, on Wed, Sep 28, 2005 at 07:55:26PM -0300, Pedro Martelletto said that
> > > No, I don't, but that's simply not needed. Just a note saying "I was
> > > running OpenBSD version
On Sat, Oct 08, 2005 at 07:32:05PM +0100, Tom Cosgrove wrote:
> As a rule of thumb, don't post to tech@ unless you are including a
> diff to fix/add something.
For (more or less obvious) fixes, isn't sendbug(1) including a diff
more appropriate than a mail to [EMAIL PROTECTED]
Ciao,
Kili
Tom Cosgrove wrote:
Andreas Bihlmaier 8-Oct-05 15:20 >>>
...
>> Now what should I do about my network card?
>> Send describtion of problem
>> 1.) to misc@ ?
>> 2.) use sendbug ?
>> 3.) to tech@ ?
>
> Plenty of bug reports start out as threads on [EMAIL PROTECTED] If you're not
> sure, ask on
>>> Andreas Bihlmaier 8-Oct-05 15:20 >>>
>
> From my point of view I can understand why people rather send their
> bugs to misc rather than use sendbug. It is the response or feedback
> they want to get before submitting plain out dumb bug reports. Most
> of the time (that is NOT only for OpenBSD)
> Guys
>
> Thanks for taking the trouble to send something more concrete about
> how to reproduce the problem.
>
> I have found the bug, and just committed the fix. The next snapshots
> will have it in, so please test, and help us make sure there are no
> side effects!
>
Thank you so much! Hosi
Guys
Thanks for taking the trouble to send something more concrete about
how to reproduce the problem.
I have found the bug, and just committed the fix. The next snapshots
will have it in, so please test, and help us make sure there are no
side effects!
Finally, to the person who said there are
>>> frantisek holop 29-Sep-05 01:23 >>>
>
> hmm, on Wed, Sep 28, 2005 at 07:55:26PM -0300, Pedro Martelletto said that
> > No, I don't, but that's simply not needed. Just a note saying "I was
> > running OpenBSD version X, kernel dated Y, on an environment Z, and
> > suddenly everything was gone" w
I can confirm this behaviour. But, I can still mount
and use the partition. I'm using 3.7.
What I get is:
1) say /mnt/ms/ directory contains 1, 2, 3 directories
with a bunch of stuff in them.
2) cd /mnt/ms/; mkdir 4; mv * 4
3) cd 4
4) ls and 1, 2, 3 gets listed.
But, if I cd into any of the
Oh Cool! I happen to be unlucky enough to have such a setup. Just for
fun I copied my /usr/local (bad idea, too big) to my fat32 partition
as provided by the instructions far below. I took a quick look around
the file structure and then immediately unmounted it, and gave it an
fsck.
=-=-=-=-=-=-=-
I don't want to heat up this discussion even further, BUT
mount a FAT32 partition somewhere and
"cp /some_folder /mnt/fat"
There should be files (the more the better) in the directory (they should NOT be
empty).
Now use "cmp" or "diff" to compare the directories. Everything still correct ?
Good
Hi Jan,
On 29/09/2005, at 4:14 PM, Jan Johansson wrote:
Let me then tell you how Windows XP flushed my USB drive to
bitheaven because i used fdisk to make a normal partition table
on it.
XP has stuffed me up too on occasion. I try to stay well away from
2000/XP Disk Manager. (Is that what it'
frantisek holop <[EMAIL PROTECTED]> wrote:
> i am sorry to see that solid fat32 support is just not a
> priority for openbsd. i can understand that, i don't imagine
> Theo has a dual boot fat32 shared partition on any of his
> machines.
Oh, come on. He is trying to fix the problem and there have
> so which part of the referenced mail you don't understand?
> (http://marc.theaimsgroup.com/?l=openbsd-misc&m=110488032901414&w=2)
> let me see:
> openbsd version: check
> kernel dated: check
> environment: check
> instructions to repeat (even though somewhat vague,
> what can you do, it's the na
Okay, whatever.
-p.
hmm, on Wed, Sep 28, 2005 at 05:28:09PM -0700, Spruell, Darren-Perot said that
> I'm with you. I can't send patches. I don't have the skillz.
but
> But I don't have your problems either. And unlike you, I *am* capable of
> sending a bug report if there is something that needs fixed. You, on the
hmm, on Wed, Sep 28, 2005 at 07:55:26PM -0300, Pedro Martelletto said that
> No, I don't, but that's simply not needed. Just a note saying "I was
> running OpenBSD version X, kernel dated Y, on an environment Z, and
> suddenly everything was gone" would be a start.
so which part of the referenced
From: frantisek holop [mailto:[EMAIL PROTECTED]
> > Want it fixed? Submit patches. Use your wide array of "reference
> > implementations" to fix it, since it's such a hot item on
> your plate.
> >
> > > forgive me my bitterness. i am mourning my lost files.
> >
> > And consequently whining lik
Pedro Martelletto wrote:
It should be of no surprise that if you don't step up and report an
issue, it won't get fixed.
As I did not know if it was an issue or if I had done something stupid
myself, I never filed a report. I have never claimed I did so. I was
wondering what hosed my filesyste
On Wed, Sep 28, 2005 at 11:44:31PM +0200, frantisek holop wrote:
> i know very well how to report bugs thank you very much.
So why didn't you?
> been on the list for quite some time now. to use your car
> repairsman example: do you expect me to wreck my car AGAIN
> so just i can report you what
hmm, on Wed, Sep 28, 2005 at 11:30:50AM -0700, Spruell, Darren-Perot said that
> No it isn't. Consider the number of people that actually *use* the
> antiquated piece of garbage file system. Now compare that to those using
> OpenBSD. Probably a small portion, no?
consider the number of people who
hmm, on Wed, Sep 28, 2005 at 05:25:11PM -0300, Pedro Martelletto said that
> bugs@ is the right place to go, preferably with a (filled) formal PR
> like the ones sendbug(1) generates for you. Having two separate lists is
> the only way we have to differentiate between the usual amount of
> discussi
http://www.openbsd.org/report.html is also an excellent source of
information on how to report issues, so they can get fixed.
-p.
Alexander and Frantisek,
It should be of no surprise that if you don't step up and report an
issue, it won't get fixed. Sending a description of the problem to misc@
is not the correct way of submitting a report. Doing so is more or less
like whispering on a large avenue that your car is broken an
From: frantisek holop [mailto:[EMAIL PROTECTED]
> i also don't understand how is it possible that operations on this
> "primitive" file system "tends to result in badness".
> especially when so much reference implementations are floating
> around (all the other bsd's, linux, embedded devices).
>
>
frantisek holop wrote:
i think mount_msdos should be disabled as of now.
it is/was causing me too much grief... i don't understand
how can be the quality of the vfat file system so bad in openbsd.
it does not go hand in hand with the great quality and stability
of the system. if nobody cares to
hmm, on Thu, Sep 15, 2005 at 12:02:42PM +0200, Alexander Hall said that
> Ted Unangst wrote:
> >On Wed, 14 Sep 2005, Alexander Hall wrote:
> >
> >
> >>I think that bad stuff happens when I move directories around. Windows
> >>checkdisk (at boot time) once complained about a lot of "." and ".."
> >
Ted Unangst wrote:
On Wed, 14 Sep 2005, Alexander Hall wrote:
I think that bad stuff happens when I move directories around. Windows
checkdisk (at boot time) once complained about a lot of "." and ".." directory
entried that were invalid. I cannot recall if this was done remotely using
shlight
On Wed, 14 Sep 2005, Alexander Hall wrote:
> I think that bad stuff happens when I move directories around. Windows
> checkdisk (at boot time) once complained about a lot of "." and ".." directory
> entried that were invalid. I cannot recall if this was done remotely using
> shlight or nfs, or loc
Forgot this:
$ grep wd0 /etc/fstab
/dev/wd0k /mnt/images msdos rw,nodev,nosuid,noexec,-m=0777,-l 0 0
$ mount | grep wd0
/dev/wd0k on /mnt/images type msdos (NFS exported, local, nodev, noexec,
nosuid, mask=0777, long)
I (Alexander Hall) wrote:
Hi all.
I wonder if anyone has any idea what co
Hi all.
I wonder if anyone has any idea what could be hosing my msdos file
system. The file system itself is "necessary" since I occasionally need
to dual-boot with windows. However, in this case, I do not believe that
windows is causing my problems.
The problem that arises is that some dire
45 matches
Mail list logo
