Here are my teaching guix videos

2020-06-03 Thread Joshua Branson
Hello,

I've been recording myself tweaking Guix and various other things and
posting the videos here:

https://video.hardlimit.com/accounts/joshua_branson/video-channels

Please note that I do not describe myself as a guix developer.  I am a
guix user, who occasionally does tiny bug reporting and documentation
patches.  If you are something of a guix newbie, then you may find
these videos helpful.

If you are an experienced guix developer, would you please consider
posting a video of your developmental workflow.  Because I am certain
that I could learn a lot from the more experienced guix developers.

Thanks,

Joshua

P.S.  Please send replies to the list and NOT my inbox.  I am
subscribed to help-guix.  Thanks.



Re: Guix System ext4 index full

2020-06-03 Thread Leo Famulari
On Wed, Jun 03, 2020 at 11:14:23PM +0200, Tobias Geerinckx-Rice wrote:
> Unfortunately, once that hash table fills up, the premier stable Linux file
> system just… gives up and refuses to write any more data.  In a very cryptic
> way.

It's so cryptic... I wonder how often people hit this limit in practice?
Is Guix the only place it happens often? Maybe we can ask the kernel
devs to improve the error reporting here.



Re: Guix System ext4 index full

2020-06-03 Thread Tobias Geerinckx-Rice

Vincent Legoll 写道:

I think the filesystem (or directory) is full of inodes.


No, but it's a similar hard limit, and one that not even ‘df -i’ 
will warn you about.


Ext4's dir_index feature uses hash tables to look up directory 
entries, so that for directories with a very large number of items 
(like /gnu/store!), the kernel doesn't have to do the horribly 
slow equivalent of:


 for i in *; do …; done

Unfortunately, once that hash table fills up, the premier stable 
Linux file system just… gives up and refuses to write any more 
data.  In a very cryptic way.


The large_dir flag ‘increases the limit’ (the man page does not 
say by how much) but it doesn't go away.


Your hash table is full of eels,

T G-R


signature.asc
Description: PGP signature


Re: Guix System ext4 index full

2020-06-03 Thread Vincent Legoll

Hello,

On 03/06/2020 22:21, Roel Janssen wrote:

Also, I cannot write to the root filesystem because the system thinks
it's full (while df shows it has ~125G free space).


T
I think the filesystem (or directory) is full of inodes.

There are many forms of foulness ;-)

--
Vincent Legoll



Guix System ext4 index full

2020-06-03 Thread Roel Janssen
Dear Guix,

I'm running Guix System and I'm getting the following messages in
dmesg:
[42457.660237] EXT4-fs warning: 7076 callbacks suppressed
[42457.660240] EXT4-fs warning (device sdd3): ext4_dx_add_entry:2335:
Directory (ino: 19796947) index full, reach max htree level :2
[42457.660242] EXT4-fs warning (device sdd3): ext4_dx_add_entry:2339:
Large directory feature is not enabled on this filesystem
[42457.697840] EXT4-fs warning (device sdd3): ext4_dx_add_entry:2335:
Directory (ino: 19796947) index full, reach max htree level :2
[42457.697842] EXT4-fs warning (device sdd3): ext4_dx_add_entry:2339:
Large directory feature is not enabled on this filesystem
[42457.697930] EXT4-fs warning (device sdd3): ext4_dx_add_entry:2335:
Directory (ino: 19796947) index full, reach max htree level :2
[42457.697931] EXT4-fs warning (device sdd3): ext4_dx_add_entry:2339:
Large directory feature is not enabled on this filesystem
[42457.702879] EXT4-fs warning (device sdd3): ext4_dx_add_entry:2335:
Directory (ino: 19796947) index full, reach max htree level :2
[42457.702880] EXT4-fs warning (device sdd3): ext4_dx_add_entry:2339:
Large directory feature is not enabled on this filesystem
[42457.703994] EXT4-fs warning (device sdd3): ext4_dx_add_entry:2335:
Directory (ino: 19796947) index full, reach max htree level :2
[42457.703995] EXT4-fs warning (device sdd3): ext4_dx_add_entry:2339:
Large directory feature is not enabled on this filesystem

I used the graphical installer to install the Guix System.

Also, I cannot write to the root filesystem because the system thinks
it's full (while df shows it has ~125G free space).

Any help would be appreciated.

Kind regards,
Roel Janssen




Re: Local definitions and Virtual machine image

2020-06-03 Thread Marius Bakke
Emmanuel Medernach  writes:

> Hello Guixers !
>
> I  created an  image with  'guix system  vm-image'
> which  contains  local  defined  packages.   These
> packages  are  present   on  the  Virtual  Machine
> however  they are  not listed  with 'guix  package
> --list-installed'.

'guix package -I' only lists packages that are installed to the user
profile.  Use 'guix package -p /run/current-system/profile -I' to see
system-installed packages.

> As  I   need  to   customize
> LD_LIBRARY_PATH, I use "guix  build" to list store
> directories  from  package   names  but  it  tries
> instead to  recompile them  even though  they  are
> already installed.

The reason 'guix build foo' gives a different result is because you have
not run 'guix pull', so you are using the "guix snapshot" from
gnu/packages/package-management.scm, which is on a fixed commit.

Whereas when you built the VM, you were likely using a newer version of
Guix.

> How to  properly export  local definitions  in the
> virtual machine image ?

There are a couple of ways around this.  One is to run 'make
update-guix-package' in the Guix source tree to update the Guix
snapshot, and use './pre-inst-env' when generating the VM.  It requires
a Guix development setup though.

Another is to look at the commit that was used to generate the VM in
/run/current-system/provenance and run 'guix pull --commit=that-commit'.

Perhaps 'guix system vm-image' could learn a '--update-guix-snapshot' to
automatically update the "system guix".  Someone would have to implement
it first though.  :-)

HTH,
Marius


signature.asc
Description: PGP signature


Re: newbe question

2020-06-03 Thread Julien Lepiller
Le 3 juin 2020 10:03:34 GMT-04:00, Adam Kandur via  a écrit :
>
>hi everyone! why when i "$ guix pull" i need to connect to
>ci.guix.gnu.org? 

It's the build farm. Guix checks for the availability of substitutes, so you 
don't have to spend hours building something that was already built.

Of course you can disable substitutes (--no-substitutes) or specify another 
substitute server if you wish (--substitute-urls).

HTH!



Re: newbe question

2020-06-03 Thread Ricardo Wurmus


Adam Kandur via  writes:

> why when i "$ guix pull" i need to connect to ci.guix.gnu.org? 

ci.guix.gnu.org provides you with binaries, so that you don’t have to
build everything from source.  By default Guix will fetch from
ci.guix.gnu.org, but you don’t have to download anything from
ci.guix.gnu.org if you don’t want to.

You can download from any other machine that runs “guix publish” or
contact the upstream servers directly to fetch source code and build
everything locally.

-- 
Ricardo



newbe question

2020-06-03 Thread Adam Kandur via


hi everyone! why when i "$ guix pull" i need to connect to ci.guix.gnu.org? 



Local definitions and Virtual machine image

2020-06-03 Thread Emmanuel Medernach
Hello Guixers !

I  created an  image with  'guix system  vm-image'
which  contains  local  defined  packages.   These
packages  are  present   on  the  Virtual  Machine
however  they are  not listed  with 'guix  package
--list-installed'.As  I   need  to   customize
LD_LIBRARY_PATH, I use "guix  build" to list store
directories  from  package   names  but  it  tries
instead to  recompile them  even though  they  are
already installed.

How to  properly export  local definitions  in the
virtual machine image ?

Best regards,

Emmanuel Medernach