Re: No space left on device ...

On Sat, May 20, 2023 at 08:12:39AM +, Albretch Mueller wrote: > On 5/17/23, Jeffrey Walton wrote: > > On Wed, May 17, 2023 at 1:06 PM Dan Ritter wrote: > >> Albretch Mueller wrote: > >> Assuming you have network access close to boot time, you might > >> want to run an NTP daemon to get the

Re: No space left on device ...

On 5/17/23, Jeffrey Walton wrote: > On Wed, May 17, 2023 at 1:06 PM Dan Ritter wrote: >> Albretch Mueller wrote: >> Assuming you have network access close to boot time, you might >> want to run an NTP daemon to get the time from a selection of >> other servers. > Nowadays, time is something that

Re: No space left on device ...

On Thu, 2023-05-18 at 10:42 -0600, Charles Curley wrote: > On Thu, 18 May 2023 10:07:05 -0400 > Default User wrote: > > > If I am running systemd-timesyncd on a single-user, internet- > > connected > > computer, not needing to serve time signals to any other device, > > would > > there be any

Re: No space left on device ...

On Thu, 18 May 2023 10:07:05 -0400 Default User wrote: > If I am running systemd-timesyncd on a single-user, internet-connected > computer, not needing to serve time signals to any other device, would > there be any reason to use ntp instead? NTP is a protocol, like TCP or UDP. One program that

Re: No space left on device ...

On Thu, 2023-05-18 at 10:20 -0400, Dan Ritter wrote: > Default User wrote: > > On Wed, 2023-05-17 at 13:48 -0600, Charles Curley wrote: > > > On Wed, 17 May 2023 12:48:28 -0400 > > > Dan Ritter wrote: > > > > > > > Assuming you have network access close to boot time, you might > > > > want to

Re: No space left on device ...

Default User wrote: > On Wed, 2023-05-17 at 13:48 -0600, Charles Curley wrote: > > On Wed, 17 May 2023 12:48:28 -0400 > > Dan Ritter wrote: > > > > > Assuming you have network access close to boot time, you might > > > want to run an NTP daemon to get the time from a selection of > > > other

Re: No space left on device ...

On Wed, 2023-05-17 at 13:48 -0600, Charles Curley wrote: > On Wed, 17 May 2023 12:48:28 -0400 > Dan Ritter wrote: > > > Assuming you have network access close to boot time, you might > > want to run an NTP daemon to get the time from a selection of > > other servers. > > Concur. > > > > >

Re: No space left on device ...

On Wed, 17 May 2023 12:48:28 -0400 Dan Ritter wrote: > Assuming you have network access close to boot time, you might > want to run an NTP daemon to get the time from a selection of > other servers. Concur. > > Debian runs a pool, which is configured by default in ntp-server > and chrony, at

Re: No space left on device ...

On Wed, May 17, 2023 at 1:06 PM Dan Ritter wrote: > > Albretch Mueller wrote: > > In case someone runs into the same problem, for some reason I can't > > quite understand "sudo hwclock --set" wasn't working. Someone helped > > me: > > > >

Re: No space left on device ...

Albretch Mueller wrote: > In case someone runs into the same problem, for some reason I can't > quite understand "sudo hwclock --set" wasn't working. Someone helped > me: > > https://manpages.debian.org/stretch/util-linux/hwclock.8.en.html > https://wiki.debian.org/DateTime > > and "date"

Re: No space left on device ...

> Yes, I did. I had to reset the BIOS to "factory settings" which also > changed the clock time which then I couldn't change with hwclock ... "Another day another problem": computer clock back to BIOS factory settings Your Computer Clock is Wrong: Your computer thinks it is 8/7/2022, which

Re: No space left on device ...

> Has this ever worked in the past? It is my understanding that the Linux NTFS > driver is read-only. > Mounting how exactly? And what is the contents of /proc/mounts? Maybe > you mounted the partition read only? Well, actually, yes. This is how I have been mounting the Windows NTFS of my

Re: No space left on device ...

Albretch Mueller writes: > I have been mounting an NTFS file system on a Windows laptop without > any problems whatsoever with a Debian Live DVD: Mounting how exactly? And what is the contents of /proc/mounts? Maybe you mounted the partition read only?

Re: No space left on device ...

Joe wrote: > > First thing to try is to boot back into Windows and see if there is a > message about the drive. If so, let Windows 'fix' it. I've had cases > where the drive was not cleanly unmounted and Linux has mounted it > read-only. Windows was able to repair it, whatever the problem was.

Re: No space left on device ...

On Sun, 14 May 2023 21:04:01 -0400 Jeffrey Walton wrote: > On Sun, May 14, 2023 at 8:32 PM Albretch Mueller > wrote: > > > > I have been mounting an NTFS file system on a Windows laptop without > > any problems whatsoever with a Debian Live DVD: > > > > $ uname -a > > Linux debian

Re: No space left on device ...

On Mon, 15 May 2023 00:32:01 + Albretch Mueller wrote: > when I try to save or download a file I consistently get the same > error message: > > $ cp "No space left on device" > No_space_left_on_device.txt > bash: No_space_left_on_device.txt: No space left on device That *shouldn't* work. I

Re: No space left on device ...

On Sun, May 14, 2023 at 8:32 PM Albretch Mueller wrote: > > I have been mounting an NTFS file system on a Windows laptop without > any problems whatsoever with a Debian Live DVD: > > $ uname -a > Linux debian 5.10.0-18-amd64 #1 SMP Debian 5.10.140-1 (2022-09-02) > x86_64 GNU/Linux > > and even

Re: "No space left on device" error, but df shows plenty of space

On Thursday, 2 February 2017 10:05:58 PYST Andy Smith wrote: > Hi Kynn, > > On Wed, Feb 01, 2017 at 10:43:37AM -0500, Kynn Jones wrote: > > On Wed, Feb 1, 2017 at 7:24 AM, Andy Smith wrote: > > > On Tue, Jan 31, 2017 at 06:42:39PM -0500, Kynn Jones wrote: > > > >

Re: "No space left on device" error, but df shows plenty of space

Hi Kynn, On Wed, Feb 01, 2017 at 10:43:37AM -0500, Kynn Jones wrote: > On Wed, Feb 1, 2017 at 7:24 AM, Andy Smith wrote: > > On Tue, Jan 31, 2017 at 06:42:39PM -0500, Kynn Jones wrote: > > > Unfortunately, I'll never know what the problem was. > > > > Do you use btrfs? > >

Re: "No space left on device" error, but df shows plenty of space

On Wed, Feb 1, 2017 at 7:24 AM, Andy Smith wrote: > Hi Kynn, > > On Tue, Jan 31, 2017 at 06:42:39PM -0500, Kynn Jones wrote: > > After the machine rebooted, I was able to run `dpkg-reconfigure ntp` > > without error. > > > > Unfortunately, I'll never know what the problem

Re: "No space left on device" error, but df shows plenty of space

Hi Kynn, On Tue, Jan 31, 2017 at 06:42:39PM -0500, Kynn Jones wrote: > After the machine rebooted, I was able to run `dpkg-reconfigure ntp` > without error. > > Unfortunately, I'll never know what the problem was. Do you use btrfs? What does "df -i" report now, after your reboot when things

Re: "No space left on device" error, but df shows plenty of space

Hi everyone! Thank you for your suggestions. They taught some new tricks. As it happened, I had to reboot the machine for an unrelated (?) reason (monitor would not wake from sleep). After the machine rebooted, I was able to run `dpkg-reconfigure ntp` without error. Unfortunately, I'll never

Re: "No space left on device" error, but df shows plenty of space

On Tue, 31 Jan 2017 08:01:00 -0500 Kynn Jones wrote: Hello Kynn, >When I tried to install `ntp`, there was a "No space left on device" at >the end of `apt-get`'s output, but `df` shows no shortage of space: I've no idea whether this is relevant to your case, but it's possible

Re: "No space left on device" error, but df shows plenty of space

Hi Kynn, On Tue, Jan 31, 2017 at 08:01:00AM -0500, Kynn Jones wrote: > Filesystem 1K-blocks Used Available Use% Mounted on > /dev/sda5 381993164 206410036 156155956 57% / […] > # dpkg-reconfigure ntp > Error: No space left on device > > How can I troubleshoot

Re: "No space left on device" error, but df shows plenty of space

On 01/31/2017 08:03 AM, Eduardo M KALINOWSKI wrote: On Ter, 31 Jan 2017, Kynn Jones wrote: Hi everyone! When I tried to install `ntp`, there was a "No space left on device" at the end of `apt-get`'s output, but `df` shows no shortage of space: Try 'df -i', you're probably out of inodes. I

Re: "No space left on device" error, but df shows plenty of space

On 01/31/2017 08:01 AM, Kynn Jones wrote: Hi everyone! When I tried to install `ntp`, there was a "No space left on device" at the end of `apt-get`'s output, but `df` shows no shortage of space: # df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda5

Re: "No space left on device" error, but df shows plenty of space

On Ter, 31 Jan 2017, Kynn Jones wrote: Hi everyone! When I tried to install `ntp`, there was a "No space left on device" at the end of `apt-get`'s output, but `df` shows no shortage of space: Try 'df -i', you're probably out of inodes. -- Eduardo M KALINOWSKI edua...@kalinowski.com.br

Re: No space left on device (28) but device is NOT full!

On Wed, Nov 6, 2013 at 4:43 PM, Neal Murphy neal.p.mur...@alum.wpi.edu wrote: On Wednesday, November 06, 2013 07:44:18 AM Wawrzek Niewodniczanski wrote: This is a bit off main topic, but definitely 'on' for this list. Lets imagine a scenario there is nothing to delete on the troublesome

Re: No space left on device (28) but device is NOT full!

On Wed, 6 Nov 2013 21:45:28 -0800 un...@physics.ubc.ca (unruh) wrote: In linux.debian.user, you wrote: On Mon, 04 Nov 2013 21:51:26 -0600 Stan Hoeppner s...@hardwarefreak.com wrote: ... Food for thought: your /dev/sda7 is an EXT filesystem of 26GB with 1.7M inodes. XFS would give

Re: No space left on device (28) but device is NOT full!

On 5 November 2013 02:30, Tazman Deville tazmande...@gmx.com wrote: On Mon, Nov 04, 2013 at 06:43:45PM -0500, Hecber Cordova wrote: Hi, Did you check inodes usage? (df -i) I could be inodes availability rather than block availability. [...] I have no idea what the significance of

Re: No space left on device (28) but device is NOT full!

On Wednesday, November 06, 2013 07:44:18 AM Wawrzek Niewodniczanski wrote: This is a bit off main topic, but definitely 'on' for this list. Lets imagine a scenario there is nothing to delete on the troublesome partition, but there is another disk. What would be the best tool to move data to

Re: No space left on device (28) but device is NOT full!

On 6 November 2013 13:43, Neal Murphy neal.p.mur...@alum.wpi.edu wrote: Assuming the problem is /var/log is part of the root filesystem and is crammed with millions of files. Assume other drive is /dev/sdb. The general process is as follows. 1. Reboot to single-user 2. Add partition #1 to

Re: No space left on device (28) but device is NOT full!

On Wed, Nov 06, 2013 at 11:43:09AM -0500, Neal Murphy wrote: 3. 'mkreiserfs /dev/sdb1' # to avoid the whole issue of inodes Before opting for ReiserFS (version 3), users would be advised to do some reading on the current level of support it attracts in the kernel, and possibly seek out some

Re: No space left on device (28) but device is NOT full!

Neal Murphy neal.p.mur...@alum.wpi.edu wrote: 3. 'mkreiserfs /dev/sdb1' # to avoid the whole issue of inodes Really? ReiserFS 3 is dead, IMHO and ReiserFS 4 was never included in any vanilla kernel. I'd suggest XFS or a properly configured ext4. Sure, ext4 has a fixed set of inodes, but

Re: No space left on device (28) but device is NOT full!

On Wednesday, November 06, 2013 12:11:33 PM Beco wrote: On 6 November 2013 13:43, Neal Murphy neal.p.mur...@alum.wpi.edu wrote: Assuming the problem is /var/log is part of the root filesystem and is crammed with millions of files. Assume other drive is /dev/sdb. The general process is as

Re: No space left on device (28) but device is NOT full!

On Mon, 04 Nov 2013 21:51:26 -0600 Stan Hoeppner s...@hardwarefreak.com wrote: ... Food for thought: your /dev/sda7 is an EXT filesystem of 26GB with 1.7M inodes. XFS would give you ~23M inodes on a 26GB filesystem. An ext[2-4] filesystem can be created with any desired number inodes by

Re: No space left on device (28) but device is NOT full!

On 11/4/2013 10:28 PM, Tazman Deville wrote: ... Got it! find . -name 'popularity-*' | xargs rm -rf (passes the files to rm one at a time). Glad you got it squared away Anthony. Normally I'd suggest filing a bug report against the problem application, but since the system is Squeeze it's

Re: No space left on device (28) but device is NOT full!

On 11/5/2013 1:21 AM, Richard Hector wrote: On 05/11/13 16:51, Stan Hoeppner wrote: Second, you have a serious problem here because it is your root filesystem that has run out of inodes. You need to ask yourself why you have 1.7M files in your rootfs. That's very dumb. Or perhaps That's

Re: No space left on device (28) but device is NOT full!

On Tue, Nov 05, 2013 at 05:28:16AM +0100, Tazman Deville wrote: find . -name 'popularity-*' | xargs rm -rf Sorry, opportunity for a bit of golf. Find has a built-in for deleting files: find . -type f -name 'popularity-*' -delete I'd also be rather wary of invoking rm -rf with the results of

Re: No space left on device (28) but device is NOT full!

Hi. On Tue, Nov 05, 2013 at 09:41:58AM +, Jonathan Dowland wrote: On Tue, Nov 05, 2013 at 05:28:16AM +0100, Tazman Deville wrote: find . -name 'popularity-*' | xargs rm -rf Sorry, opportunity for a bit of golf. Find has a built-in for deleting files: find . -type f -name

Re: No space left on device (28) but device is NOT full!

On Tue, Nov 05, 2013 at 02:52:52AM -0600, Stan Hoeppner wrote: On 11/5/2013 1:21 AM, Richard Hector wrote: On 05/11/13 16:51, Stan Hoeppner wrote: Second, you have a serious problem here because it is your root filesystem that has run out of inodes. You need to ask yourself why you have

Re: No space left on device (28) but device is NOT full!

On Tue, Nov 05, 2013 at 09:41:58AM +, Jonathan Dowland wrote: On Tue, Nov 05, 2013 at 05:28:16AM +0100, Tazman Deville wrote: find . -name 'popularity-*' | xargs rm -rf Sorry, opportunity for a bit of golf. Find has a built-in for deleting files: find . -type f -name 'popularity-*'

Re: No space left on device (28) but device is NOT full!

On Tue, Nov 05, 2013 at 03:13:10PM +0400, Reco wrote: Hi. On Tue, Nov 05, 2013 at 09:41:58AM +, Jonathan Dowland wrote: On Tue, Nov 05, 2013 at 05:28:16AM +0100, Tazman Deville wrote: find . -name 'popularity-*' | xargs rm -rf Sorry, opportunity for a bit of golf. Find has a

Re: No space left on device (28) but device is NOT full!

On Tue, Nov 05, 2013 at 03:13:10PM +0400, Reco wrote: perl -e 'for(popularity-*){((stat)[9](unlink))}' I have two questions. Why before unlink and why stat[9] there? stat[9] is mtime. Regards, /Lars -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of

Re: No space left on device (28) but device is NOT full!

On Tue, Nov 05, 2013 at 03:13:10PM +0400, Reco wrote: find . -type f -name 'popularity-*' -print0 | xargs -0rn 20 rm -f I idly wonder (don't know) to what extend find might parallelize the unlinks with -delete. A cursory scan of the semantics would suggest it could potentially do so: it's not

Re: No space left on device (28) but device is NOT full!

On Tue, Nov 05, 2013 at 02:29:10PM +, Jonathan Dowland wrote: On Tue, Nov 05, 2013 at 03:13:10PM +0400, Reco wrote: find . -type f -name 'popularity-*' -print0 | xargs -0rn 20 rm -f I idly wonder (don't know) to what extend find might parallelize the unlinks with -delete. A cursory scan

Re: No space left on device (28) but device is NOT full!

Hi. On Tue, Nov 05, 2013 at 04:25:13PM +0200, Lars Noodén wrote: On Tue, Nov 05, 2013 at 03:13:10PM +0400, Reco wrote: perl -e 'for(popularity-*){((stat)[9](unlink))}' I have two questions. Why before unlink and why stat[9] there? You have to pass unlink something to delete. Stat is

Re: No space left on device (28) but device is NOT full!

On 11/05/2013 05:33 PM, Reco wrote: Hi. On Tue, Nov 05, 2013 at 04:25:13PM +0200, Lars Noodén wrote: On Tue, Nov 05, 2013 at 03:13:10PM +0400, Reco wrote: perl -e 'for(popularity-*){((stat)[9](unlink))}' I have two questions. Why before unlink and why stat[9] there? You have to pass

Re: No space left on device (28) but device is NOT full!

On Tue, Nov 05, 2013 at 07:15:19PM +0400, Reco wrote: On Tue, Nov 05, 2013 at 02:29:10PM +, Jonathan Dowland wrote: On Tue, Nov 05, 2013 at 03:13:10PM +0400, Reco wrote: find . -type f -name 'popularity-*' -print0 | xargs -0rn 20 rm -f I idly wonder (don't know) to what extend find

Re: No space left on device (28) but device is NOT full!

On Tue, Nov 05, 2013 at 04:54:19PM +, Jonathan Dowland wrote: The binary size effects the initial load-up time which, for small numbers of files/short execution times, may be the lions share of the total execution time. However as you point out, for orders of magnitute like 500,000; it's

Re: No space left on device (28) but device is NOT full!

On Tue, Nov 5, 2013 at 11:29 AM, Tazman Deville tazmande...@gmx.com wrote: On Tue, Nov 05, 2013 at 08:34:37AM +0900, Joel Rees wrote: [...] The first thing that I check when I get disk full errors but the disks are not full is the permissions. And the second thing should be the inodes, but I

Re: No space left on device (28) but device is NOT full!

On Tue, Nov 5, 2013 at 8:16 AM, Tazman Deville tazmande...@gmx.com wrote: Just since yesterday, I'm seeing this PHP error meaning the No space left on device (28) you mention in the subject, I suppose. on the scuttle installation on a little server here I have. Scuttle is installed from the

Re: No space left on device (28) but device is NOT full!

Hi, Did you check inodes usage? (df -i) I could be inodes availability rather than block availability. Best regards, HC On Mon, Nov 4, 2013 at 6:16 PM, Tazman Deville tazmande...@gmx.com wrote: Just since yesterday, I'm seeing this PHP error on the scuttle installation on a little server

Re: No space left on device (28) but device is NOT full!

On Tue, Nov 05, 2013 at 08:34:37AM +0900, Joel Rees wrote: On Tue, Nov 5, 2013 at 8:16 AM, Tazman Deville tazmande...@gmx.com wrote: Just since yesterday, I'm seeing this PHP error meaning the No space left on device (28) you mention in the subject, I suppose. on the scuttle

Re: No space left on device (28) but device is NOT full!

On Mon, Nov 04, 2013 at 06:43:45PM -0500, Hecber Cordova wrote: Hi, Did you check inodes usage? (df -i) I could be inodes availability rather than block availability. AHA! I have no idea what the significance of this is, but df -i gives $ df -i FilesystemInodes

Re: No space left on device (28) but device is NOT full!

Hi, inodes are basically metadata (http://www.linfo.org/inode.html). It looks like you have a lot of files in the root directory (most probably small files), and your system has used all available inodes. You cannot add more inodes without re-creating the file system (mkfs), this is because the

Re: No space left on device (28) but device is NOT full!

On 11/4/2013 8:30 PM, Tazman Deville wrote: On Mon, Nov 04, 2013 at 06:43:45PM -0500, Hecber Cordova wrote: Hi, Did you check inodes usage? (df -i) I could be inodes availability rather than block availability. AHA! I have no idea what the significance of this is, but df -i

Re: No space left on device (28) but device is NOT full!

On Mon, Nov 04, 2013 at 09:51:26PM -0600, Stan Hoeppner wrote: On 11/4/2013 8:30 PM, Tazman Deville wrote: On Mon, Nov 04, 2013 at 06:43:45PM -0500, Hecber Cordova wrote: Hi, Did you check inodes usage? (df -i) I could be inodes availability rather than block availability.

Re: No space left on device (28) but device is NOT full!

On Tue, Nov 05, 2013 at 05:14:34AM +0100, Tazman Deville wrote: On Mon, Nov 04, 2013 at 09:51:26PM -0600, Stan Hoeppner wrote: On 11/4/2013 8:30 PM, Tazman Deville wrote: On Mon, Nov 04, 2013 at 06:43:45PM -0500, Hecber Cordova wrote: Hi, Did you check inodes usage? (df -i)

Re: No space left on device (28) but device is NOT full!

On 05/11/13 16:51, Stan Hoeppner wrote: Second, you have a serious problem here because it is your root filesystem that has run out of inodes. You need to ask yourself why you have 1.7M files in your rootfs. That's very dumb. Or perhaps That's not generally advisable. or similar. Richard

Re: No space left on device (28) but device is NOT full!

On Tuesday, November 05, 2013 02:21:36 AM Richard Hector wrote: On 05/11/13 16:51, Stan Hoeppner wrote: Second, you have a serious problem here because it is your root filesystem that has run out of inodes. You need to ask yourself why you have 1.7M files in your rootfs. That's very dumb.

Re: No space left on device.

Guillaume Yziquel guillaume.yziq...@citycable.ch à écrit le Sat, 07 Nov 2009 10:33:45 +0100 Salut. Après avoir fait une mise à jour du noyau, j'obtiens les messages d'erreurs suivants. Comment résout-on un truc comme cela? gzip: stdout: No space left on device update-initramfs: failed

Re: No space left on device.

On Sat, Nov 07, 2009 at 10:33:45AM +0100, Guillaume Yziquel wrote: Salut. Après avoir fait une mise à jour du noyau, j'obtiens les messages d'erreurs suivants. Comment résout-on un truc comme cela? [...] W: Possible missing firmware /lib/firmware/tigon/tg3.bin for module tg3 gzip:

Re: No space left on device - Solved!

Hi again! I finally fixed the problem by creating two new partitions, one for /home (~26.5 Gb) and one for /var (~512 Mb). Here are the steps I followed (suggested by David Bree): 0. Reboot the computer using parted boot floppy. 1. Invoke parted and resize hda5 by shrinking it down to 10

Re: No space left on device

Hello Salman! At Sunday 20 July 2003 03:20 Salman Haq wrote: Thanks everybody for your helpful responses. To make some temporary room I cleaned up some logs and unnecessary directories in a few of the home directories of some of the users. Then I resolved to fix the problem once and

Re: No space left on device

On Sat, Jul 19, 2003 at 09:10:14PM -0400, Salman Haq wrote: #df -h FilesystemSize Used Avail Use% Mounted on /dev/hda3 463M 440M 1.0k 100% / /dev/hda5 37G 2.5G 32G 8% /usr # df -ih FilesystemInodes IUsed IFree

Re: No space left on device

On Mon, 14 Jul 2003, Bijan Soleymani wrote: On Mon, Jul 14, 2003 at 12:51:55PM -0400, Salman Haq wrote: Hi, When trying to compile some code, I got the following error: cpp0: /tmp/ccFJJwQN.ii: No space left on device I then realized that /tmp is mounted on my root partition,

Re: No space left on device

--TiqCXmo5T1hvSQQg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 14, 2003 at 12:51:55PM -0400, Salman Haq wrote: =20 Hi, =20 When trying to compile some code, I got the following error: =20 cpp0:

Re: No space left on device

Hello Salman Haq wrote: When trying to compile some code, I got the following error: cpp0: /tmp/ccFJJwQN.ii: No space left on device I then realized that /tmp is mounted on my root partition, which was full: #df -h FilesystemSize Used Avail Use% Mounted on /dev/hda3

Re: No space left on device

BS == Bijan Soleymani [EMAIL PROTECTED] writes: BS On Mon, Jul 14, 2003 at 12:51:55PM -0400, Salman Haq wrote: Hi, When trying to compile some code, I got the following error: cpp0: /tmp/ccFJJwQN.ii: No space left on device I then realized that /tmp is

Re: No space left on device

* Salman Haq [EMAIL PROTECTED] [14-07-2003 18:56]: Now, I realize that this a very bad partition scheme but I'm just a newbie. When I was installing debian a few months ago, I didn't intend to have this scheme. I wanted root to be mounted as '/' and everything else under '/usr' since thats