Re: no space left on device

entries. > > On Tuesday, 04-02-2025 at 07:22 Stefan Monnier wrote: > > >> Jan 13 19:46:06 eagle ntfs-3g[4262]: No free mft record for $MFT: No > > >> space left on device > > > Hmm, MFT too small? A quick search showed me this (from a forum): > > &g

Re: no space left on device

:22 Stefan Monnier wrote: > >> Jan 13 19:46:06 eagle ntfs-3g[4262]: No free mft record for $MFT: No > >> space left on device > > Hmm, MFT too small? A quick search showed me this (from a forum): > > AFAIK the MFT is implemented as a "normal" file; it can gr

Re: no space left on device

>> Jan 13 19:46:06 eagle ntfs-3g[4262]: No free mft record for $MFT: No >> space left on device > Hmm, MFT too small? A quick search showed me this (from a forum): AFAIK the MFT is implemented as a "normal" file; it can grow as needed like any other file. So, as long as

Re: no space left on device

A big thank you to everybody for all the hints and support. Unfortunately I was pressured to wipe the drive and use elsewhere. Therefore I couldn't continue with any further experiments :-(

Re: no space left on device

On 1/20/25 11:15, Adam Weremczuk wrote: > Also: > > sudo mount -t exfat /dev/nvme0n1 /mnt/nvme0n1 > mount: /mnt/nvme0n1: wrong fs type, bad option, bad superblock on /dev/ > nvme0n1, missing codepage or helper program, or other error. > > makes no difference. If it thinks exfat is the wrong type,

Re: no space left on device

On 20/01/2025 23:37, Max Nikulin wrote: On 20/01/2025 23:29, Hans wrote: Am Montag, 20. Januar 2025, 17:15:40 CET schrieb Adam Weremczuk: Try "chkdsk /F /R C:" in windows, this should help. Perhaps some tool already "repaired" the drive and some filesystem structure is really corrupted by e.g

Re: no space left on device

On 1/20/25 05:37, Adam Weremczuk wrote: I don't think it's fake but it's the lack of partition being the main issue. I've just reconnected it to the previous system and found this in history: sudo mkfs.exfat /dev/nvme0n1 sudo mkdir /mnt/nvme0n1 sudo mount /dev/nvme0n1 /mnt/nvme0n1 I think the

Re: no space left on device

Am Montag, 20. Januar 2025, 17:39:19 CET schrieb Adam Weremczuk: > I'm unable to mount the disk in Windows without formatting to assigne a > letter, so can't do "chkdsk ... C:" No, you do NOT have to mount the drive. Just boot windows into rescue mode and then got to the DOSshell and do chckdsk on

Re: no space left on device

I'm unable to mount the disk in Windows without formatting to assigne a letter, so can't do "chkdsk ... C:" Windows just reports something that looks like two blank partitions, both with 2TB of unallocated space. Please see a screenshot attached to my message from about 4.5 hrs ago showing that.

Re: no space left on device

On 20/01/2025 23:29, Hans wrote: Am Montag, 20. Januar 2025, 17:15:40 CET schrieb Adam Weremczuk: Try "chkdsk /F /R C:" in windows, this should help. Perhaps some tool already "repaired" the drive and some filesystem structure is really corrupted by e.g. mbr code. You may try to get somethin

Re: no space left on device

On Mon, Jan 20, 2025 at 16:15:40 +, Adam Weremczuk wrote: > Also: > > sudo mount -t exfat /dev/nvme0n1 /mnt/nvme0n1 > mount: /mnt/nvme0n1: wrong fs type, bad option, bad superblock on > /dev/nvme0n1, missing codepage or helper program, or other error. > > makes no difference. I still suspect

Re: no space left on device

Am Montag, 20. Januar 2025, 17:15:40 CET schrieb Adam Weremczuk: Try "chkdsk /F /R C:" in windows, this should help. If you do not own a windows computer, then you can use any windows-live-cd for that, like Falcon4, HirensBootCD or UBCD4Win. Hans > Also: > > sudo mount -t exfat /dev/nvme0n1 /

Re: no space left on device

Am Montag, 20. Januar 2025, 17:04:52 CET schrieb Adam Weremczuk: I am not sure, but this looks very weired for me. What are these loop- partitions? It looks like you are usinng an Ubuntu-Livesystem, do you? I am not much friend of Ubuntu, as they sometimes do weired things (IMHO), but if I unders

Re: no space left on device

Also: sudo mount -t exfat /dev/nvme0n1 /mnt/nvme0n1 mount: /mnt/nvme0n1: wrong fs type, bad option, bad superblock on /dev/nvme0n1, missing codepage or helper program, or other error. makes no difference. On 20/01/2025 16:04, Adam Weremczuk wrote: Yes, /dev/nvme0n1 comes from the onboard M2

Re: no space left on device

Yes, /dev/nvme0n1 comes from the onboard M2 socket (where the drive was populated with data) and /dev/sdb comes from USB adaptor used to connect the same drive to a different Ubuntu desktop. Output from the first (/dev/nvme0n1 on board) loadout. $ sudo lsblk --fs -o +SIZE NAMEFSTYPE FSVE

Re: no space left on device

On 20/01/2025 20:37, Adam Weremczuk wrote: sudo mount /dev/nvme0n1 /mnt/nvme0n1 mount: /mnt/nvme0n1: wrong fs type, bad option, bad superblock on /dev/ nvme0n1, missing codepage or helper program, or other error. Is it for the drive plugged directly into a M.2 slot or through a USB adapter?

Re: no space left on device

I don't think it's fake but it's the lack of partition being the main issue. I've just reconnected it to the previous system and found this in history: sudo mkfs.exfat /dev/nvme0n1 sudo mkdir /mnt/nvme0n1 sudo mount /dev/nvme0n1 /mnt/nvme0n1 I think the fact that it reported as nvme0n1 cofused

Re: no space left on device

On Mon, Jan 20, 2025 at 13:01:35 +, Adam Weremczuk wrote: > Please see the attached illustrating that, no destructive steps taken yet. > > On 20/01/2025 12:55, Adam Weremczuk wrote: > > Gparted seems to recognise the fact that 53% of space has data written > > to it. It also knows about the ex

Re: no space left on device

There are fake 4TB drives in the market. Maybe you got one? There are some tools available for checking this (I believe, in Debian there is a tool called "f3" or similar. If there are no important data on the drive, you might reformat the drive to ext2/3/4 and then use "resize2fs" to corect the

Re: no space left on device

Please see the attached illustrating that, no destructive steps taken yet. On 20/01/2025 12:55, Adam Weremczuk wrote: Gparted seems to recognise the fact that 53% of space has data written to it. It also knows about the extfat system. This morning, when I viewed the drive through gparted on a ne

Re: no space left on device

How about the data already written to the unpartitioned disk? It doesn't sound like either of the paths gives me any hope. I don't care about the data or wiping the drive later as soon as I copy existing content over to WS 2019 local NTFS drive. But I can't afford to spend 3 days again processi

Re: no space left on device

On Mon, Jan 20, 2025 at 11:56:19 +, Adam Weremczuk wrote: > Now when I try to mount the NVMe on a different Ubuntu system (through USB > adapter) I get: > > $sudo mount /dev/sdb /mnt/sdb > mount: /mnt/sdb: wrong fs type, bad option, bad superblock on /dev/sdb, > missing codepage or helper prog

Re: no space left on device

On Jan 20, 2025, Adam Weremczuk wrote: > Hi all, > > An update on my struggle. > > I followed the extfat path but I likely somehow make a noobish mistake > and a partition was not created... > > Despite that, I was able to mount it an copy all the data across to it! > > Now when I try to mount

Re: no space left on device

Hi all, An update on my struggle. I followed the extfat path but I likely somehow make a noobish mistake and a partition was not created... Despite that, I was able to mount it an copy all the data across to it! Now when I try to mount the NVMe on a different Ubuntu system (through USB adap

Re: no space left on device

On Wed, Jan 15, 2025 at 10:43:57AM -0500, Michael Stone wrote: > On Wed, Jan 15, 2025 at 05:53:18AM +0100, to...@tuxteam.de wrote: [...] > > It is most probably that the NTFS is running out of mft records, a > > resource you set up when making the ntfs file system [...] > I'm skeptical of this a

Re: no space left on device

On Wed, Jan 15, 2025 at 05:53:18AM +0100, to...@tuxteam.de wrote: On Tue, Jan 14, 2025 at 03:26:17PM -0500, Michael Stone wrote: On Tue, Jan 14, 2025 at 06:13:44PM +, Adam Weremczuk wrote: > I'm giving exfat a shot and so far I'm impressed with 160 MB/s average > transfer rate (HDD -> NVMe).

Re: about output from mount (was: no space left on device)

Felix Miata writes: > I have the following in ~/.bashrc for making that easier: > > alias Mnt='mount | egrep -v "cgroup|rpc|ramfs|tmpfs|^sys|on /dev|on /proc|on > /sys|on /var" | sort ' mount | fgrep -vf <(awk '/^nodev/{print $2}' /proc/filesystems) urs

Re: no space left on device

On Wed, 2025-01-15 at 11:51 +0100, Nicolas George wrote: > Jeffrey Walton (12025-01-15): > > Using compression to minimize writes is part of a write leveling > > strategy to extend drive life. > > . > > So you say, and all you have to qu

Re: no space left on device

On Wed, Jan 15, 2025 at 5:51 AM Nicolas George wrote: > > Jeffrey Walton (12025-01-15): > > Using compression to minimize writes is part of a write leveling > > strategy to extend drive life. > > . > > So you say, and all you have to quo

Re: no space left on device

Jeffrey Walton (12025-01-15): > Using compression to minimize writes is part of a write leveling > strategy to extend drive life. > . So you say, and all you have to quote for it is a Google search result page. This is how far I am willi

Re: no space left on device

On Wed, Jan 15, 2025 at 5:04 AM Nicolas George wrote: > > Jeffrey Walton (12025-01-15): > > > > > > Probably better since disk controllers often use compression to > > > > > > minimize writes and blocks written during a write cycle. > > > > Using a random stream during zeroization due to write com

Re: no space left on device

Jeffrey Walton (12025-01-15): > > > > > Probably better since disk controllers often use compression to > > > > > minimize writes and blocks written during a write cycle. > > Using a random stream during zeroization due to write compression has > been a security control for at least 15 years. This

Re: no space left on device

On Wed, Jan 15, 2025 at 4:46 AM Nicolas George wrote: > > Jeffrey Walton (12025-01-15): > > Reliably Erasing Data from Flash-Based Solid State Drives, > > , > > The word compression does not appear in this document. Would you be so >

Re: no space left on device

Jeffrey Walton (12025-01-15): > Reliably Erasing Data from Flash-Based Solid State Drives, > , The word compression does not appear in this document. Would you be so kind as to explain why you considered it relevant? > Practical Eras

Re: no space left on device

On Wed, Jan 15, 2025 at 3:58 AM Nicolas George wrote: > > Jeffrey Walton (12025-01-15): > > Probably better since disk controllers often use compression to > > minimize writes and blocks written during a write cycle. > > I find that statement highly dubious. Do you have a source? Reliably Erasing

Re: no space left on device

Jeffrey Walton (12025-01-15): > Probably better since disk controllers often use compression to > minimize writes and blocks written during a write cycle. I find that statement highly dubious. Do you have a source? Regards, -- Nicolas George

Re: no space left on device

I also have another idea: It looks for me, the user wants to get the data on an notebook with NVME and later copy it to a Windows 2019. If so, I personally would do it in naother way using a lifesystem. I would boot a live system and format the NVME with ext4. As the source and the target ist

Re: no space left on device

On Wed, Jan 15, 2025 at 1:37 AM David Christensen wrote: > > On 1/14/25 10:13, Adam Weremczuk wrote: > > On 14/01/2025 17:02, Michael Stone wrote: > >> On Tue, Jan 14, 2025 at 03:30:17PM +, Adam Weremczuk wrote: > >>> I need NTFS to connect it to a WS 2019 machine later. > >> ... (Storage frau

Re: no space left on device

On Tue, Jan 14, 2025 at 03:26:17PM -0500, Michael Stone wrote: > On Tue, Jan 14, 2025 at 06:13:44PM +, Adam Weremczuk wrote: > > I'm giving exfat a shot and so far I'm impressed with 160 MB/s average > > transfer rate (HDD -> NVMe). > > > > That's significantly faster than before. > > > > Par

Re: no space left on device

On 1/14/25 19:42, Andy Smith wrote: Hi David, On Tue, Jan 14, 2025 at 07:28:28PM -0800, David Christensen wrote: I suggest that you unmount any filesystems on the SSD and then fill the SSD with random bytes using dd(1). If the purpose of this is to check that the full capacity of the NVMe is

Re: no space left on device

Hi David, On Tue, Jan 14, 2025 at 07:28:28PM -0800, David Christensen wrote: > I suggest that you unmount any filesystems on the SSD and then fill the SSD > with random bytes using dd(1). If the purpose of this is to check that the full capacity of the NVMe is working, the f3 tool that is already

Re: no space left on device

On 1/14/25 10:13, Adam Weremczuk wrote: On 14/01/2025 17:02, Michael Stone wrote: On Tue, Jan 14, 2025 at 03:30:17PM +, Adam Weremczuk wrote: I need NTFS to connect it to a WS 2019 machine later. ... (Storage fraud really is a thing, where people sell drives that have less storage than rep

Re: no space left on device

On 1/14/25 12:03, Michael Stone wrote: On Tue, Jan 14, 2025 at 03:30:17PM +, Adam Weremczuk wrote: I need NTFS to connect it to a WS 2019 machine later. Have you considered exfat? Support for that on linux is much better than ntfs. At the very least I'd format the drive as anything ot

Re: no space left on device

On Tue, Jan 14, 2025 at 06:13:44PM +, Adam Weremczuk wrote: I'm giving exfat a shot and so far I'm impressed with 160 MB/s average transfer rate (HDD -> NVMe). That's significantly faster than before. Partially because I'm using "rsync -avh --no-perms --no-group --no-owner ..." this time.

Re: no space left on device

I bought the drive from Amazon and everything looks very genuine. Nvme tool reports: $ sudo nvme list Node SN Model Namespace Usage Format FW Rev - ---

Re: no space left on device

On Tue, Jan 14, 2025 at 04:40:12PM +0100, Hans wrote: > Am Dienstag, 14. Januar 2025, 16:25:02 CET schrieb Adam Weremczuk: > > > Syslog reveals this: > > > > Jan 13 19:46:06 eagle ntfs-3g[4262]: No free mft record for $MFT: No > > space left on device > >

Re: no space left on device

On Tue, Jan 14, 2025 at 03:25:02PM +, Adam Weremczuk wrote: > All files copied were under 500 MB in size each, guaranteed. > > No dmesg entries from around the copy failure time. > > Syslog reveals this: > > Jan 13 19:46:06 eagle ntfs-3g[4262]: No free mft record for

Re: no space left on device

On Tue, Jan 14, 2025 at 03:30:17PM +, Adam Weremczuk wrote: I need NTFS to connect it to a WS 2019 machine later. Have you considered exfat? Support for that on linux is much better than ntfs. At the very least I'd format the drive as anything other than ntfs and retry as suggested elsewh

Re: no space left on device

>> Is it some kind of NVMe temp garbage overhead? No, it's a problem at the ntfs-3g level, not the NVMe level. > Possibly. I haven't been following the thread very attentively and have no > particular expertise, but maybe you are running to an issue similar to > the one described in the link bel

Re: no space left on device

On 1/14/25 10:30, Adam Weremczuk wrote: > On 14/01/2025 15:14, Hans wrote: >> >> It looks like Adam wants to copy a Windows system to another drive. Maybe he >> could delete hyberfile.sys, pagefile.sys and swapfile.sys before rsyncing. >> >> These are not necessary and will be recreated at boot fro

Re: no space left on device

Greg Wooledge wrote: > On Tue, Jan 14, 2025 at 15:25:02 +, Adam Weremczuk wrote: > > Jan 13 19:46:06 eagle ntfs-3g[4262]: No free mft record for $MFT: No space > > left on device > > Jan 13 19:46:15 eagle ntfs-3g[4262]: message repeated 3154 times: [ No free > > mf

Re: no space left on device

On Tue, Jan 14, 2025 at 15:25:02 +, Adam Weremczuk wrote: > Jan 13 19:46:06 eagle ntfs-3g[4262]: No free mft record for $MFT: No space > left on device > Jan 13 19:46:15 eagle ntfs-3g[4262]: message repeated 3154 times: [ No free > mft record for $MFT: No space left on device

Re: no space left on device

Hi Adam, Adam Weremczuk writes: > All files copied were under 500 MB in size each, guaranteed. > > No dmesg entries from around the copy failure time. > > Syslog reveals this: > > Jan 13 19:46:06 eagle ntfs-3g[4262]: No free mft record for $MFT: No > space left on device

Re: no space left on device

On Tue, Jan 14, 2025 at 10:15 AM Hans wrote: > > Good idea, Klaus! > > It looks like Adam wants to copy a Windows system to another drive. Maybe he > could delete hyberfile.sys, pagefile.sys and swapfile.sys before rsyncing. Wow! That's a bit drastic, how about "rsync ... --exclude-from=FILENAME

Re: no space left on device

Am 14.01.25 um 16:30 schrieb Adam Weremczuk: I need NTFS to connect it to a WS 2019 machine later. I thought it would be easier than fiddling with WSL or pay for something like: https://www.paragon-software.com/home/linuxfs-windows/ (which seems decent) Why do you connect the HD to 2019

Re: no space left on device

of data to that drive (26+ > million files, tens of thousands of folders, about 2TB in total). > > I copied from an internal 8TB SATA HDD formatted with ext4. > > After running for several hours, it refused to continue due to "no space > left on device". > > I

Re: no space left on device

Am Dienstag, 14. Januar 2025, 16:25:02 CET schrieb Adam Weremczuk: > Syslog reveals this: > > Jan 13 19:46:06 eagle ntfs-3g[4262]: No free mft record for $MFT: No > space left on device Hmm, MFT too small? A quick search showed me this (from a forum): No

Re: no space left on device

I need NTFS to connect it to a WS 2019 machine later. I thought it would be easier than fiddling with WSL or pay for something like: https://www.paragon-software.com/home/linuxfs-windows/ (which seems decent) On 14/01/2025 15:14, Hans wrote: Good idea, Klaus! It looks like Adam wants to cop

Re: no space left on device

All files copied were under 500 MB in size each, guaranteed. No dmesg entries from around the copy failure time. Syslog reveals this: Jan 13 19:46:06 eagle ntfs-3g[4262]: No free mft record for $MFT: No space left on device Jan 13 19:46:06 eagle ntfs-3g[4262]: message repeated 40 times: [ No

Re: no space left on device

Hi Adam, On Tue, Jan 14, 2025 at 02:32:25PM +, Adam Weremczuk wrote: > "FUSEBLK" is just how an NTFS partition is reported via the "mount" command, > among others. This is how NTFS-3g operates. It is normal. Hence, as long as > you have permission to mount and access the device, it's OK, and y

Re: no space left on device

Good idea, Klaus! It looks like Adam wants to copy a Windows system to another drive. Maybe he could delete hyberfile.sys, pagefile.sys and swapfile.sys before rsyncing. These are not necessary and will be recreated at boot from Windows next time. Just an idea Hans > My assumption is: thi

Re: no space left on device

On Tue, Jan 14, 2025 at 03:58:50PM +0100, Klaus Singvogel wrote: > Adam Weremczuk wrote: > > > > The command was: > > > > rsync -av /mnt/sdb1/data-mirror/ /mnt/nvme0n1p1/data-mirror/ --progress > > --delete > > If you're running out of disk space, use option "--delete-before" instead of > "--d

Re: no space left on device

Adam Weremczuk wrote: > > The command was: > > rsync -av /mnt/sdb1/data-mirror/ /mnt/nvme0n1p1/data-mirror/ --progress > --delete If you're running out of disk space, use option "--delete-before" instead of "--delete" But the option --delete-before is more dangerous, as you might loose files,

Re: no space left on device

On Tue, Jan 14, 2025 at 09:48:36AM -0500, Stefan Monnier wrote: > > After running for several hours, it refused to continue due to "no space > > left on device". > > I've confirmed the problem trying to save a text file there, same error. > > Hmm... I d

Re: no space left on device

Adam Weremczuk wrote: > The last few line before termination were: > > 47,997 100%2.29MB/s0:00:00 (xfr#19403697, to-chk=0/25525501) > rsync: [receiver] mkstemp > "/mnt/nvme0n1p1/data-mirror/20241231/.task_id.OyhQxa" failed: No space left > on device (28) &g

Re: about output from mount (was: no space left on device)

Greg Wooledge composed on 2025-01-14 07:30 (UTC-0500): > Finally, please show the mount options of whatever file system is > full. This means grepping something out of the output of "mount". > It can be difficult to get the right line sometimes. I have the following in ~/.bashrc for making that

Re: no space left on device

> After running for several hours, it refused to continue due to "no space > left on device". > I've confirmed the problem trying to save a text file there, same error. Hmm... I don't see anything amiss in the data you sent, so I'm afraid I don't know wha

Re: no space left on device

Hi Hans, You are incorrect, the source (directory) is 2TB in size: root@eagle:~# du -sh /mnt/sdb1/data-mirror 2.0T/mnt/sdb1/data-mirror and the destination drive (started blank and empty) reported 3.7 TB capacity. The question is why rsync and disk space tools disagree whether there sho

Re: no space left on device

Am 14.01.25 um 15:12 schrieb Greg Wooledge: ntfs partition is reported via the "mount" command, among others. So this is an NTFS file system that you're writing to? I think that's got to be related to your problems somehow. Maybe you're exceeding some limit in the Linux NTFS driver (singl

Re: no space left on device

Google says: When an NTFS partition is reported as "FUSEBLK", it means that the partition is being mounted with the FUSE file system in userspace. This is normal and allows non-root users to read and write to the partition. "FUSEBLK" is just how an NTFS partition is reported via the "mount"

Re: no space left on device

Source is sdb1, target is nvme0n1p1 > rsync -av /mnt/sdb1/data-mirror/ /mnt/nvme0n1p1/data-mirror/ --progress > --delete > root@eagle:~# df -h /mnt/nvme0n1p1 > Filesystem Size Used Avail Use% Mounted on > /dev/nvme0n1p1 3.7T 1.1T 2.6T 30% /mnt/nvme0n1p1 Your target has 1,1 TB free. >

Re: no space left on device

On Tue, Jan 14, 2025 at 14:05:46 +, Adam Weremczuk wrote: > Mount options of the destination as requested: > > root@eagle:~# mount | grep /mnt/nvme0n1p1 > /dev/nvme0n1p1 on /mnt/nvme0n1p1 type fuseblk > (rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096) What on earth is a fuseblk? G

Re: no space left on device

Hi Greg, The last few line before termination were: 47,997 100%2.29MB/s0:00:00 (xfr#19403697, to-chk=0/25525501) rsync: [receiver] mkstemp "/mnt/nvme0n1p1/data-mirror/20241231/.task_id.OyhQxa" failed: No space left on device (28) sent 1,889,449,185,360 bytes received 3

Re: no space left on device

On Tue, Jan 14, 2025 at 11:49:25 +, Adam Weremczuk wrote: > After running for several hours, it refused to continue due to "no space > left on device". > > I've confirmed the problem trying to save a text file there, same error. Please show us all of the details, *

Re: no space left on device

On Tue, Jan 14, 2025 at 11:49:25AM +, Adam Weremczuk wrote: > I started copying (with rsync) a large chunk of data to that drive (26+ > million files, tens of thousands of folders, about 2TB in total). > That much has been copied so far: > > find /mnt/nvme0n1p1 -type f | wc -l > 19868844 Th

no space left on device

about 2TB in total). I copied from an internal 8TB SATA HDD formatted with ext4. After running for several hours, it refused to continue due to "no space left on device". I've confirmed the problem trying to save a text file there, same error. That much has been copied so far:

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 ti

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 rea

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 ru

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 ser

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. > > > > > Debi

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 l

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: > > > > https://manpages.debian.org/stretch/util-linux/hwclock.8.

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" wo

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 pre

Re: No space left on device ...

s NTFS of my laptop and my employer's as well without any problems whatsoever. I just open the file browser/viewer and click the drive to mount it in order to unmount, eject it you right click on it. It works. >> $ cp "No space left on device" > No_space_left_on_device.txt >

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. Oh

Re: No space left on device ...

0F Sun 14 May 2023 07:13:43 PM UTC > > 166G/media/user/60320G593EB7250F > > > > real0m45.230s > > user 0m1.073s > > sys 0m15.443s > > $ > > > > when I try to save or download a file I consistently get the same > > error message: > > &

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 devi

Re: No space left on device ...

hen 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 started happening right after a WiFi connection at a

No space left on device ...

7:13:43 PM UTC 166G/media/user/60320G593EB7250F real0m45.230s user0m1.073s sys 0m15.443s $ 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:

Re: question regarding no space left on device message

Hi, Semih Ozlem wrote: > However I do not know how to install new programs in knoppix > (still there is apt-get install as a command, but debian packages > no longer seem to work, and I do not know which packages work with > knoppix system, [...] https://www.knopper.net/knoppix/knoppix861-en.ht

Re: question regarding no space left on device message

Hi Thomas, Thank you for your email and recommendation. It seems that knoppix uses less ram. However I do not know how to install new programs in knoppix (still there is apt-get install as a command, but debian packages no longer seem to work, and I do not know which packages work with knoppix sys

Re: question regarding no space left on device message

Hi, Semih Ozlem wrote: > I used "dd if=isofilename of=devicename" So the partition table afterwards is the one which came with the ISO. MBR based, but accompanied by an invalid GPT. Further, this implies that your Live system is only running on RAM and not using a writable system disk.

Re: question regarding no space left on device message

Also if one creates a partition on some device, say /dev/sda becomes /dev/sda1 /dev/sda2 /dev/sda3 after partitioning (which can be done with gnome disk utility, or gparted, or from the command line, and I forget the exact commands now probably "parted mkpart") then "dd if=isofilename.iso of=/dev/s

Re: question regarding no space left on device message

I used "dd if=isofilename of=devicename" and when using this command I use a blank usb or one with a partition, and device name gets filled with the partition that will be overwritten if anything was previously on it. Thomas Schmitt , 21 Ağu 2020 Cum, 14:14 tarihinde şunu yazdı: > Hi, > > Semih O

Re: question regarding no space left on device message

Hi, Semih Ozlem wrote: > Hi Thomas, (You need to reply to the list, not to my mail address directly.) > the computer has 4gb RAM This should suffice for a RAM based session. But if you add large software packages, then 4 GB for everything will at some point not be enough. > https://cdimage.d

  1   2   >