Sqlite3 err: disk I/O error: invalid argument in Linux 2.6.36.4brcmarm armv7l GNU/Linux ARM Cortex-A9 #13855

@lunny commented on GitHub (Dec 20, 2024):

Linux kernel 2.6.36.4 should be supported by Golang v1.23, but will not be in Golang v1.24.

@lunny commented on GitHub (Dec 20, 2024): Linux kernel 2.6.36.4 should be supported by Golang v1.23, but will not be in Golang v1.24.

GiteaMirror commented

@techknowlogick commented on GitHub (Dec 20, 2024):

I believe Gitea only supports down to kernel version 3.0 due to how we compile our binaries for CGO

@techknowlogick commented on GitHub (Dec 20, 2024): I believe Gitea only supports down to kernel version 3.0 due to how we compile our binaries for CGO

GiteaMirror commented

@LipsonX commented on GitHub (Dec 20, 2024):

it's so sad... it seems well but only sqlite currently.

@LipsonX commented on GitHub (Dec 20, 2024): it's so sad... it seems well but only sqlite currently.

GiteaMirror commented

@lunny commented on GitHub (Dec 20, 2024):

Maybe #32628 can resolve this.

@lunny commented on GitHub (Dec 20, 2024): Maybe #32628 can resolve this.

GiteaMirror commented

@LipsonX commented on GitHub (Dec 20, 2024):

Maybe #32628 can resolve this.

I found gitea hard to set up cross-compilation env. especially the gcc. is there a docker or some way for me to build with #32628.
Or some help?

@LipsonX commented on GitHub (Dec 20, 2024): > Maybe #32628 can resolve this. I found gitea hard to set up cross-compilation env. especially the gcc. is there a docker or some way for me to build with [#32628](https://github.com/go-gitea/gitea/pull/32628). Or some help?

GiteaMirror commented

@lunny commented on GitHub (Dec 20, 2024):

#32628 will not depend on CGO. So you can cross-compile easily.
GOOS=linux CGO_ENABLED=0 GOARCH=arm5 TAGS="bindata" make build.

@lunny commented on GitHub (Dec 20, 2024): #32628 will not depend on CGO. So you can cross-compile easily. `GOOS=linux CGO_ENABLED=0 GOARCH=arm5 TAGS="bindata" make build`.

GiteaMirror commented

@LipsonX commented on GitHub (Dec 20, 2024):

I try branch master merge #32628

run GOOS=linux CGO_ENABLED=0 GOARCH=arm5 TAGS="bindata" make build

and out put:

Running go generate...
bindata for migration already up-to-date
bindata for options already up-to-date
bindata for public already up-to-date
bindata for templates already up-to-date
go: unsupported GOOS/GOARCH pair linux/arm5
CGO_CFLAGS=" -DSQLITE_MAX_VARIABLE_NUMBER=32766" go build -v  -tags 'bindata' -ldflags '-s -w  -X "main.MakeVersion=GNU Make 4.2.1" -X "main.Version=1.24.0+dev-20-g91f481fa7a" -X "main.Tags=bindata"' -o gitea
go: unsupported GOOS/GOARCH pair linux/arm5
make: *** [Makefile:799: gitea] Error 2

I try GOOS=linux CGO_ENABLED=0 GOARCH=arm TAGS="bindata" make build. it builds success but it may be a arm64. Binary cannot be run.

do i miss something. go is not my major.

@LipsonX commented on GitHub (Dec 20, 2024): I try branch master merge #32628 run `GOOS=linux CGO_ENABLED=0 GOARCH=arm5 TAGS="bindata" make build` and out put: ``` Running go generate... bindata for migration already up-to-date bindata for options already up-to-date bindata for public already up-to-date bindata for templates already up-to-date go: unsupported GOOS/GOARCH pair linux/arm5 CGO_CFLAGS=" -DSQLITE_MAX_VARIABLE_NUMBER=32766" go build -v -tags 'bindata' -ldflags '-s -w -X "main.MakeVersion=GNU Make 4.2.1" -X "main.Version=1.24.0+dev-20-g91f481fa7a" -X "main.Tags=bindata"' -o gitea go: unsupported GOOS/GOARCH pair linux/arm5 make: *** [Makefile:799: gitea] Error 2 ``` I try `GOOS=linux CGO_ENABLED=0 GOARCH=arm TAGS="bindata" make build`. it builds success but it may be a arm64. Binary cannot be run. do i miss something. `go` is not my major.

GiteaMirror commented

@eeyrjmr commented on GitHub (Dec 20, 2024):

GOARM=5 GOARCH=arm

That should select the correct architecture

@eeyrjmr commented on GitHub (Dec 20, 2024): GOARM=5 GOARCH=arm That should select the correct architecture

GiteaMirror commented

@hiifong commented on GitHub (Dec 20, 2024):

I try branch master merge #32628

run GOOS=linux CGO_ENABLED=0 GOARCH=arm5 TAGS="bindata" make build

and out put:
Running go generate...
bindata for migration already up-to-date
bindata for options already up-to-date
bindata for public already up-to-date
bindata for templates already up-to-date
go: unsupported GOOS/GOARCH pair linux/arm5
CGO_CFLAGS=" -DSQLITE_MAX_VARIABLE_NUMBER=32766" go build -v  -tags 'bindata' -ldflags '-s -w  -X "main.MakeVersion=GNU Make 4.2.1" -X "main.Version=1.24.0+dev-20-g91f481fa7a" -X "main.Tags=bindata"' -o gitea
go: unsupported GOOS/GOARCH pair linux/arm5
make: *** [Makefile:799: gitea] Error 2
I try GOOS=linux CGO_ENABLED=0 GOARCH=arm TAGS="bindata" make build. it builds success but it may be a arm64. Binary cannot be run.

do i miss something. go is not my major.

You can use the file command to view the format information of the executable file.

@hiifong commented on GitHub (Dec 20, 2024): > I try branch master merge #32628 > > run `GOOS=linux CGO_ENABLED=0 GOARCH=arm5 TAGS="bindata" make build` > > and out put: > > ``` > Running go generate... > bindata for migration already up-to-date > bindata for options already up-to-date > bindata for public already up-to-date > bindata for templates already up-to-date > go: unsupported GOOS/GOARCH pair linux/arm5 > CGO_CFLAGS=" -DSQLITE_MAX_VARIABLE_NUMBER=32766" go build -v -tags 'bindata' -ldflags '-s -w -X "main.MakeVersion=GNU Make 4.2.1" -X "main.Version=1.24.0+dev-20-g91f481fa7a" -X "main.Tags=bindata"' -o gitea > go: unsupported GOOS/GOARCH pair linux/arm5 > make: *** [Makefile:799: gitea] Error 2 > ``` > > I try `GOOS=linux CGO_ENABLED=0 GOARCH=arm TAGS="bindata" make build`. it builds success but it may be a arm64. Binary cannot be run. > > do i miss something. `go` is not my major. You can use the file command to view the format information of the executable file. ![image](https://github.com/user-attachments/assets/8e016adf-9598-44d1-8e7d-a329410cd52c)

GiteaMirror commented

@LipsonX commented on GitHub (Dec 20, 2024):

GOARM=5 GOARCH=arm

That should select the correct architecture

Thanks to eeyrjmr. it's right. I have been build a arm5 version with go pure sqlite and it can be run in my device. And, "disk I/O error" happend again.

I also write a demo only use ncruces/go-sqlite3 and it also cause "disk I/O error". I maybe figure it out next time.

it's a well try, at least. #32628 so good for droping cgo. However, makefile need some modify, like gcc flags.

@LipsonX commented on GitHub (Dec 20, 2024): > GOARM=5 GOARCH=arm > > That should select the correct architecture Thanks to [eeyrjmr](https://github.com/eeyrjmr). it's right. I have been build a arm5 version with go pure sqlite and it can be run in my device. And, "disk I/O error" happend again. I also write a demo only use [ncruces/go-sqlite3](https://github.com/ncruces/go-sqlite3) and it also cause "disk I/O error". I maybe figure it out next time. it's a well try, at least. #32628 so good for droping cgo. However, makefile need some modify, like gcc flags.

GiteaMirror commented

@ncruces commented on GitHub (Dec 20, 2024):

On Linux my SQLite driver uses OFD locks, which showed up in Linux 3.15 (2017, all currently supported versions have it).
Given the complexity of supporting POSIX advisory locks, this is unlikely to change.

On other systems, my advice would be to try the sqlite3_dotlk build tag which should work everywhere Go does.

Just be careful that, if you use build tags, don't do database maintenance while gitea is running (no Litestream, no online backups, no vacuuming the database using the sqlite3 shell, etc), or you will corrupt your data.

@ncruces commented on GitHub (Dec 20, 2024): On Linux my SQLite driver uses OFD locks, which showed up in Linux 3.15 (2017, all currently supported versions have it). Given the complexity of supporting [POSIX advisory locks](https://github.com/sqlite/sqlite/blob/b74eb0/src/os_unix.c#L1073-L1161), this is unlikely to change. On other systems, my advice would be to try the `sqlite3_dotlk` [build tag](https://github.com/ncruces/go-sqlite3/blob/main/vfs/README.md#build-tags) which should work everywhere Go does. Just be careful that, if you use build tags, don't do database maintenance while gitea is running (no Litestream, no online backups, no vacuuming the database using the `sqlite3` shell, etc), or you will corrupt your data.

GiteaMirror commented

@LipsonX commented on GitHub (Dec 21, 2024):

On Linux my SQLite driver uses OFD locks, which showed up in Linux 3.15 (2017, all currently supported versions have it). Given the complexity of supporting POSIX advisory locks, this is unlikely to change.

On other systems, my advice would be to try the sqlite3_dotlk build tag which should work everywhere Go does.

Just be careful that, if you use build tags, don't do database maintenance while gitea is running (no Litestream, no online backups, no vacuuming the database using the sqlite3 shell, etc), or you will corrupt your data.

thanks bro. it works in my ncruces go-sqlite demo and gitea.

gitea build with #32628: GOOS=linux CGO_ENABLED=0 GOARM=5 GOARCH=arm TAGS="bindata sqlite sqlite3_dotlk" make build. it can run. but some other problem. it runs seriously slow. see below:

I'll try next. maybe with cgo version sqlite or postgresql.

@LipsonX commented on GitHub (Dec 21, 2024): > On Linux my SQLite driver uses OFD locks, which showed up in Linux 3.15 (2017, all currently supported versions have it). Given the complexity of supporting [POSIX advisory locks](https://github.com/sqlite/sqlite/blob/b74eb0/src/os_unix.c#L1073-L1161), this is unlikely to change. > > On other systems, my advice would be to try the `sqlite3_dotlk` [build tag](https://github.com/ncruces/go-sqlite3/blob/main/vfs/README.md#build-tags) which should work everywhere Go does. > > Just be careful that, if you use build tags, don't do database maintenance while gitea is running (no Litestream, no online backups, no vacuuming the database using the `sqlite3` shell, etc), or you will corrupt your data. thanks bro. it works in my ncruces go-sqlite demo and gitea. gitea build with #32628: `GOOS=linux CGO_ENABLED=0 GOARM=5 GOARCH=arm TAGS="bindata sqlite sqlite3_dotlk" make build`. it can run. but some other problem. it runs seriously slow. see below: ![CPU{@BF9(~P0YUJLU95P00](https://github.com/user-attachments/assets/ee6c3c1a-230b-4d35-bf42-88ba5606c12a) I'll try next. maybe with cgo version sqlite or postgresql.

GiteaMirror commented

@ncruces commented on GitHub (Dec 21, 2024):

It's possible the SQLite driver is to blame. The performance depends on the JIT compiler which only supports amd64 and arm64. See the support matrix:
https://github.com/ncruces/go-sqlite3/wiki/Support-matrix

@ncruces commented on GitHub (Dec 21, 2024): It's possible the SQLite driver is to blame. The performance depends on the JIT compiler which only supports amd64 and arm64. See the support matrix: https://github.com/ncruces/go-sqlite3/wiki/Support-matrix

GiteaMirror commented

@LipsonX commented on GitHub (Dec 22, 2024):

hi everyone. I try more case. flow is my result

Linux 2.6.36.4 armv7l with Pure Go Lite solutions, There is some data race maybe:

solution	result
gitea + ncruces/go-sqlite3 #32628	sql excution very slow
gitea +modernc.org/sqlite #20614	may work. need change sqlite3 -> sqlite. But data race discussed by #20614
gitea + glebarez/sqlite	works, need change sqlite3 -> sqlite. and fast than ncruces/go-sqlite3. Also data race maybe.

And. gitea cost lost of memory likely 200+MB. I think that maybe many one like me to see a low cost self-host git server. so Gogs could be better. Gogs cost like 20~30MB. Is't better to create a new issue for this resource cost? Maybe some build tagsis better for poor device building?

So. I fork gogs and fix some security problems waiting gitea to be better. thanks bro.

gitea + glebarez/sqlite result:

@LipsonX commented on GitHub (Dec 22, 2024): hi everyone. I try more case. flow is my result Linux 2.6.36.4 armv7l with Pure Go Lite solutions, There is some data race maybe: | solution | result | | -------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | | gitea + [ncruces/go-sqlite3](https://github.com/ncruces/go-sqlite3) [#32628](https://github.com/go-gitea/gitea/pull/32628) | sql excution very slow | | gitea +modernc.org/sqlite [#20614](https://github.com/go-gitea/gitea/pull/20614) | may work. need change sqlite3 -> sqlite. But data race discussed by [#20614](https://github.com/go-gitea/gitea/pull/20614) | | gitea + [glebarez/sqlite](https://github.com/glebarez/sqlite) | works, need change sqlite3 -> sqlite. and fast than [ncruces/go-sqlite3](https://github.com/ncruces/go-sqlite3). Also data race maybe. | And. gitea cost lost of memory likely 200+MB. I think that maybe many one like me to see a low cost self-host git server. so Gogs could be better. Gogs cost like 20~30MB. Is't better to create a new issue for this resource cost? Maybe some build tagsis better for poor device building? So. I fork gogs and fix some security problems waiting gitea to be better. thanks bro. gitea + glebarez/sqlite result: ![image](https://github.com/user-attachments/assets/23dc4c7a-384a-4ce7-bd3e-b0e6d69c3af9)

GiteaMirror commented