Re: Ext2 issues in current

[Mike]

Thanks. I'll try.


On Sat, Aug 20, 2016 at 08:38:11AM +0700, Robert Elz wrote:
> 
> gin...@email.su said:
> | General info: Host system-amd64 (yesterday's "clean" -current build) 
> 
> Try again with a more recent current.   ext2fs has been broken since it
> started to get some GSoC code incorporated in it (yes, I think about 2
> weeks ago) for ext4 filesystem support I beliebe - many ext2fs tests
> have been failing.
> 
> There have been people working on it however, and the tests now seem
> to all work (as of a few hours ago).
> 
> I don't have any ext2fs filesystems, and I haven't been doing any of the
> work, but I have been monitoring the status of the system tests recently.
> That is, I can't confirm that it is fixed now, but it might well be.
> 
> kre
> 

Re: Ext2 issues in current

[Christos Zoulas]

In article <20160821004610.GA1302@netbox.brkly.local.domain>,
Mike   wrote:
>-=-=-=-=-=-
>
>Hi Folks.
>It seems to me that last changes in  completly broke NetBSD's
>write support on it (in expected way, as it used to work for a very
> long time before). I started having troubles about 2 weeks ago. 
>At that time, I was hoping that this is just a temporary issue in
>-current, and probably will be fixed soon...But now I'm not so sure,
> since the problem is still there.
>General info: Host system-amd64 (yesterday's "clean" -current build)
> 
>So, basicaly I have the following picture today:
>
>1). A few partitions with ext2 filesystem. (Used to provide some
>  interoperability with other OS's, although I'm using only netbsd,
>  ~90% of time...and this partitions are also being used as read-only,
>  most of the time. But sometimes I'd like to have write support as well!.
>
> I created them(mostly), using only netbsd native tools. (It still did not
>  work very smoothly, but worked quite acceptably for a while).
>
> -features list : resize_inode filetype sparse_super large_file.
> -fs revision   : 1.  Of course, since I want to be able to put(sometimes)
>  large files there...
>
>2). Latest netbsd-current system
>
>3). In Read-Only mode it works normally
>
>4). Write support is still present... But works totally weird...
>   (_absolutely_ sure that It is just _new_,  _netbsd_ , trouble
> - not hardware or anything else). 
>
>In the attached text file, I wrote typical  shell session, demonstrating
>it's "work" in the rw mode(not the worst case, cause with latest changes
> it looks more like loterea- you never know what exactly you'll get,
> trying to use  ext2fs rw. Most common result is total freezed system with
> need to hard-reset..-> -> fsck and finally -> some pieces of data,
> more or less, written on disk. when using kernel-level driver, I mean.
> If using rump, tipically it will crash quckly...resulting -dirty filesystem.
> Esplecially, when writing big amounts of data and/or under high disk
>  IO load, etc)
>  
>Just wondering - Is that a known behavior?

I think it broke as part of the GSoC changes were committed. I also think
that Jaromir fixed it yesterday, but I am not sure yet.

christos

Ext2 issues in current

[Mike]

Hi Folks.
It seems to me that last changes in  completly broke NetBSD's
write support on it (in expected way, as it used to work for a very
 long time before). I started having troubles about 2 weeks ago. 
At that time, I was hoping that this is just a temporary issue in
-current, and probably will be fixed soon...But now I'm not so sure,
 since the problem is still there.
General info: Host system-amd64 (yesterday's "clean" -current build)
 
So, basicaly I have the following picture today:

1). A few partitions with ext2 filesystem. (Used to provide some
  interoperability with other OS's, although I'm using only netbsd,
  ~90% of time...and this partitions are also being used as read-only,
  most of the time. But sometimes I'd like to have write support as well!.

 I created them(mostly), using only netbsd native tools. (It still did not
  work very smoothly, but worked quite acceptably for a while).

 -features list : resize_inode filetype sparse_super large_file.
 -fs revision   : 1.  Of course, since I want to be able to put(sometimes)
  large files there...

2). Latest netbsd-current system

3). In Read-Only mode it works normally

4). Write support is still present... But works totally weird...
   (_absolutely_ sure that It is just _new_,  _netbsd_ , trouble
 - not hardware or anything else). 

In the attached text file, I wrote typical  shell session, demonstrating
it's "work" in the rw mode(not the worst case, cause with latest changes
 it looks more like loterea- you never know what exactly you'll get,
 trying to use  ext2fs rw. Most common result is total freezed system with
 need to hard-reset..-> -> fsck and finally -> some pieces of data,
 more or less, written on disk. when using kernel-level driver, I mean.
 If using rump, tipically it will crash quckly...resulting -dirty filesystem.
 Esplecially, when writing big amounts of data and/or under high disk
  IO load, etc)
  
Just wondering - Is that a known behavior?

mike@somewhere (/mnt)% ls -la
drwxr-xr-x  16 root   wheel 512 Aug 19 06:51 .
drwxr-xr-x  23 root   wheel 512 Aug 19 13:08 ..
drwxr-xr-x   2 root   wheel 512 Jul 19 21:00 MEDIA
-rw-r--r--   1 root   wheel  1016698880 Aug 13 23:59 netbsdi386.tar
mike@somewhere (/mnt)% file -s /dev/wd1j
 /dev/wd1j: Linux rev 1.0 ext2 filesystem data, 
UUID=575163fb-3aac-b04a-a4fa-af88e3f2d615, volume name "media" (large files)
mike@somewhere (/mnt)% sudo mount -t ext2fs -o noatime,rw /dev/wd1j MEDIA
mike@somewhere (/mnt)% df -h MEDIA
 Filesystem Size   Used  Avail %Cap Mounted on
/dev/wd1j   24G13G   9.6G  57% /mnt/MEDIA
mike@somewhere (/mnt)% cd MEDIA/mike
mike@somewhere (/mnt/MEDIA/mike)% ls -la
total 8
drwxr-xr-x   2 mike  wheel  4096 Aug 19 15:26 .
drwxr-xr-x  24 mike  wheel  4096 Aug 19 15:26 ..
mike@somewhere (/mnt/MEDIA/mike)% tar -tvf ../../netbsdi386.tar
drwxr-xr-x  2 mikewsrc   0 Jan  1  2016 NetBSD-i386
drwxr-xr-x  2 mikewsrc   0 Dec 21  2015 NetBSD-i386/CURRENT
-rw-r--r--  1 mikewsrc45791024 Dec 21  2015 NetBSD-i386/CURRENT/base.tgz
-rw-r--r--  1 mikewsrc71293268 Dec 21  2015 NetBSD-i386/CURRENT/comp.tgz
-rw-r--r--  1 mikewsrc  584458 Dec 21  2015 NetBSD-i386/CURRENT/etc.tgz
-rw-r--r--  1 mikewsrc 3217114 Dec 21  2015 
NetBSD-i386/CURRENT/games.tgz
-rw-r--r--  1 mikewsrc  163531 Dec 21  2015 
NetBSD-i386/CURRENT/INSTALL.HTML
-rw-r--r--  1 mikewsrc10943912 Dec 21  2015 NetBSD-i386/CURRENT/man.tgz
-rw-r--r--  1 mikewsrc 5247129 Dec 21  2015 NetBSD-i386/CURRENT/misc.tgz
-rw-r--r--  1 mikewsrc 8291700 Dec 21  2015 
NetBSD-i386/CURRENT/modulesi386.tgz
-rw-r--r--  1 mikewsrc18169481 Dec 21  2015 
NetBSD-i386/CURRENT/netbsd-GENERIC
drwxr-xr-x  2 mikewsrc   0 Dec 21  2015 NetBSD-i386/CURRENT/sources
-rw-r--r--  1 mikewsrc   394386844 Dec 21  2015 
NetBSD-i386/CURRENT/sources/src.tar.gz
-rw-r--r--  1 mikewsrc  62 Dec 21  2015 
NetBSD-i386/CURRENT/sources/src.tar.gz.MD5
-rw-r--r--  1 mikewsrc   121243902 Dec 21  2015 
NetBSD-i386/CURRENT/sources/xsrc.tar.gz
-rw-r--r--  1 mikewsrc  63 Dec 21  2015 
NetBSD-i386/CURRENT/sources/xsrc.tar.gz.MD5
-rw-r--r--  1 mikewsrc 6682693 Dec 21  2015 
NetBSD-i386/CURRENT/tests.tgz
-rw-r--r--  1 mikewsrc 2763307 Dec 21  2015 NetBSD-i386/CURRENT/text.tgz
-rw-r--r--  1 mikewsrc 7463654 Dec 21  2015 
NetBSD-i386/CURRENT/xbase.tgz
-rw-r--r--  1 mikewsrc12835820 Dec 21  2015 
NetBSD-i386/CURRENT/xcomp.tgz
-rw-r--r--  1 mikewsrc   25132 Dec 21  2015 NetBSD-i386/CURRENT/xetc.tgz
-rw-r--r--  1 mikewsrc32787195 Dec 21  2015 
NetBSD-i386/CURRENT/xfont.tgz
-rw-r--r--  1 mikewsrc12593931 Dec 21  2015 
NetBSD-i386/CURRENT/xserver.tgz
drwxr-xr-x  2 mikewsrc   0 Dec 21  2015 NetBSD-i386/STABLE-sets
-rw-r--r--  1 mikewsrc46139618 Dec 21  2015 
NetBSD-i386/STABLE-sets/base.tgz